LICENSE MANAGEMENT SYSTEM, SALES MANAGEMENT APPARATUS AND LICENSE MANAGEMENT APPARATUS

专利摘要:
license management system, sales management device and license management device describes a license management system that includes a sales management device and a license management device. the sales management apparatus includes a transmission unit that transmits a registration request including configuration information for a group including a combination of several selected programs; a product registration unit that receives an entry of the license information corresponding to the group, associates and stores the license information with the group, in a product information storage unit as product information; and a sales management unit that transits a list of product information in response to a receipt of a purchase request to purchase the program, the product information being stored in the product information storage unit. the license management apparatus includes a group information storage unit that stores the configuration information included in the registration request.
公开号:BR112012010660B1
申请号:R112012010660-0
申请日:2010-11-02
公开日:2020-12-15
发明作者:Tatsuo Ito
申请人:Ricoh Company, Ltd；
IPC主号:

专利说明:

Technical Field
[0001] The present invention relates to a license management system, a sales management system, a license management device, a license management method and a program. More specifically, the present invention relates to a license management system, a sales management system, a license management device, a license management method and a program that manages program licenses used on devices. Background of the Invention
[0002] Recently, there are some imaging devices mainly called a multifunctional device or a fax machine for which new programs can be developed and on which such a developed program can be installed. If the installation of such programs or licenses that allow the use of the programs could be provided to users according to the users' ways of using it, it would become convenient for users and it would be expected that the program providers could improve / create business opportunities also.
[0003] For example, patent document 1 discloses a license management and similar method capable of limiting the imaging apparatus capable of using a program to predetermined imaging apparatus. According to a technique in patent document 1, it is possible to change a charge amount according to the number of devices using the program. In addition, it is also possible to prevent unauthorized use of a program caused by illegal copying of the program.
[0004] On the other hand, there may be some cases where a group of programs is offered, each of the programs being able to be distributed separately and the licenses of the programs being able to be managed separately. In such cases, it is general practice that the permissible combinations of programs are determined in a unified way.
[0005] Patent document 1 - Japanese open patent application no. 2008-016013 Description of the Invention Problems to be solved by the invention
[0006] However, for example, when a program selling area is across countries in the world or when there are several types of users, there is a possibility that a set of effective programs for users differs depending on the sales areas and types of users.
[0007] The present invention is made in the light of the above circumstances, and can provide a license management system, a sales management system, a license management appliance, a license management method, and a program capable of improve a degree of freedom in combinations of programs as a distribution unit. Means to Solve Problems
[0008] In accordance with an aspect of the present invention, a license management system includes a sales management appliance and a license management appliance that manages a license for a program sold by the sales management appliance. In addition, the sales management device included a transmission unit that displays a list of information for one or more programs, and transmits a registration request to the license management device, the registration request including configuration information for a group including a combination of several of the programs selected from the programs in the information list; a product information storage unit; a product registration unit that receives a license information entry corresponding to the group, associates the license information with the group, and stores the license information associated with the group in the product information storage unit as product information ; and a sales management unit that transmits a list of product information in response to a receipt of a purchase request to purchase the programs, the product information being stored in the product information storage unit. In addition, the license management apparatus includes a group information storage unit that stores the configuration information included in the registration request.
[0009] In such a license management apparatus, it may become possible to improve a degree of freedom in combinations of programs as a distribution unit. Effects of the Present Invention
[0010] In accordance with an embodiment of the present invention, it may become possible to improve a degree of freedom in combinations of programs as a distribution unit. Brief Description of the Drawings Figure 1 is a drawing showing an exemplary configuration of an equipment management system according to a first embodiment of the present invention; Figure 2 is a drawing showing an exemplary configuration of a sales package; Figure 3 is a drawing showing an exemplary configuration of sales package information; Figure 4 is another drawing showing an exemplary configuration of sales package information; Figure 5 is a drawing showing an exemplary functional configuration of the equipment management system according to the embodiment of the present invention; Figure 6 is a drawing showing an exemplary hardware configuration of a license management server in accordance with an embodiment of the present invention; Figure 7 is a drawing showing an exemplary hardware configuration of an image forming apparatus according to an embodiment of the present invention; Figure 8 is a sequence diagram illustrating a product information registration process by a sales server; Figure 9 is a drawing showing an exemplary configuration of a sales site master; Figure 10 is a drawing showing an exemplary configuration of a product information editing screen; Figure 11 is a drawing showing an exemplary configuration of a sales package master; Figure 12 is a drawing showing an exemplary configuration of a group ID master; Figure 13 is a drawing showing an exemplary configuration of a group name master; Figure 14 is a drawing showing an exemplary configuration of a product master on the sales server; Figure 15 is a sequence diagram illustrating a procedure for processing a generation process to generate a group; Figure 16 is a drawing showing an example of a group editing screen; Figure 17 is a drawing illustrating a procedure for processing a group registration process; Figure 18 is a sequence diagram illustrating a processing procedure when a product is sold; Figure 19 is a flow chart illustrating a procedure for processing a product key generation process by a product key issuing section; Figure 20 is a drawing showing an exemplary configuration of a license management table; Figure 21 is a drawing showing an exemplary configuration of a product key; Figure 22 is a sequence diagram illustrating a processing procedure when a sales package is installed; Figure 23 is a drawing showing an example of displaying a function expansion definition menu screen; Figure 24 is a drawing showing an example of displaying a product key entry screen; Figure 25 is a drawing showing an example of displaying an error screen when a product key is invalid; Figure 26 is a drawing showing an exemplary configuration of a component management table; Figure 27 is a drawing showing an example of displaying an installation list screen; Figure 28 is a drawing showing an exemplary configuration of an installation information management table; Figure 29 is a drawing showing an example of displaying a confirmation screen when there is no problem with the dependency relationship; Figure 30 is a drawing showing an example of displaying the confirmation screen when a dependent package can be installed simultaneously; Figure 31 is a drawing showing an example of displaying the confirmation screen when a dependent package cannot be installed simultaneously; Figure 32 is a drawing showing an exemplary configuration of a license file; Fig. 33 is a flow chart illustrating a processing procedure for a verification process of verifying the dependency relationship by a component server section and a processing procedure for a generation process for generating confirmation screen data; Figure 34 is a drawing showing an exemplary configuration of a dependency relationship management table; Figure 35 is a flow chart illustrating a procedure for processing a license file generation process by an activation server section; Fig. 36 is a flow chart illustrating a procedure for processing a process for installing a sales package by the image forming apparatus; Figure 37 is a flow chart illustrating a process for calculating a license expiration date (valid period); Fig. 38 is a sequence diagram illustrating a procedure for processing a license update process; Figure 39 is a drawing showing an example of displaying an expansion function management screen; Figure 40 is a drawing showing an example of a license update / purchase screen display; Fig. 41 is a sequence diagram illustrating a procedure for processing a sales package update process; Figure 42 is a drawing showing an example of displaying an update list screen; Fig. 43 is a sequence diagram illustrating a procedure for processing a deactivation process; Fig. 44 is a flow chart illustrating a procedure for processing an automatic execution process of performing deactivation on the image forming apparatus; Fig. 45 is a sequence diagram illustrating a procedure for processing a group edit process; Fig. 46 is a drawing illustrating a procedure for processing a group modification process; Fig. 47 is a drawing illustrating a procedure for processing a group deletion process; Figure 48 is a drawing showing an exemplary configuration of an equipment management system according to a second embodiment of the present invention; Fig. 49 is a drawing showing an exemplary functional configuration of an equipment management apparatus according to the second embodiment of the present invention; Fig. 50 is a sequence diagram illustrating a procedure for processing the installation and activation of the sales package according to the second embodiment of the present invention; Fig. 51 is a sequence diagram illustrating a procedure for processing the uninstallation and deactivation of the sales package according to the second embodiment of the present invention; Fig. 52 is a drawing showing an exemplary configuration of an equipment management system according to a third embodiment of the present invention; and Figure 53 is a drawing showing an exemplary functional configuration of an equipment management apparatus in accordance with the third embodiment of the present invention. Description of Reference Numbers 1, 2 - Equipment management system 10 - License management server 11 - Activation server section 15 - Component server section 20 - Sales server 21 - Product registration section 22 - Section sales management 23 - product master 24 - product key transmission section 30 download server 31 - download processing section 32 - sales package management section 40 - imaging apparatus 41 - controller 42 - Scanner 43 - Printer 44 - Modem 45 - Operator panel 46 - Network interface 47 - SD card partition 50 - User PC 51 - Network browser 60 - Equipment management device 65 - Network client terminal 100 - Device drive 101 - Recording media 102 - Auxiliary storage device 103 - Memory device 104 - CPU 105 - Interface device 111 - Sales server cooperation section 112 - Emi section product key signature 113 - Product key verification section 115 - License issue section 116 - Deactivation section 117 - Sales server authentication section 118 - Sales site master 119 - Sales package master 120 - Group ID master 121 - License management table 122 - Group name master 151 - Dependency relationship determination section 152 - Installation support section 153 - Package update support section 154 - Management section component 155 - Component management table 411 - CPU 412 - RAM 413 - ROM 414 - HDD 421 - Installation section 422 - License update section 423 - Package update section 424 - License check section 425 - Section deactivation 426 - UI control section 427 - Installation information management table 428 - Network server section 611 - UI control section 612 - Packet information acquisition section 613 - Acquisition section Equipment information o 614 - Installation destination receiving section 615 - Validity verification section 616 - Package acquisition section 617 - License acquisition section 618 - Installation control section 619 - Destination determination section uninstall 620 - disable control section 621 - uninstall control section 651 - network browser B - bus Best Mode for Carrying Out the Invention
[0011] In the following, the embodiments of the present invention are described with reference to the accompanying drawings. Figure 1 illustrates an exemplary configuration of an equipment management system according to a first embodiment of the present invention. As shown in figure 1, an equipment management system 1 mainly includes two system environments: an E1 user environment and an E2 manufacturer environment. User environment E1 and manufacturer environment E2 are connected to each other via a wide area network 80.
[0012] The user environment E1 is a system environment for a user (customer) of an imaging device 40 as an installation target device. For example, the user environment E1 corresponds to a company or an office of the user of the imaging device 40. The user environment E1 includes one or more imaging devices 40 and one or more user PCs 50. The Imaging apparatus 40 is a multifunctional apparatus having various functions such as a printer, scanner, copier, fax machine and the like in a single chassis of the apparatus. However, the imaging apparatus 40 may have only one of these functions. It is assumed that the function of the imaging apparatus 40 can be expanded or similar by adding or updating a software component (hereinafter it can be simplified as a "component"). User PC 50 is used to perform a purchase procedure to purchase a component to be added to the imaging apparatus 40. The E1 user environment can include multiple user environments depending on the number of users (the number of users per company or office).
[0013] On the other hand, the E2 manufacturer environment is a vendor-side system environment that sells a component to be added to the imaging apparatus 40. For example, the E2 manufacturer environment can be managed by the manufacturer of the imaging apparatus 40. The manufacturer environment includes a license management server 10, a sales server 20 and a download server 30. Sales server 20 is a computer that receives a purchase order to purchase one component from the user environment E1 and corresponds to an example of a sales management apparatus according to this embodiment of the present invention. Sales servers 20 are arranged in each of the sales areas (for example, USA, Europe, Japan, Asia excluding Japan and the like) where imaging devices 40 are sold, and receive purchase orders from the environment user E1 that belongs to the sales areas in charge of the corresponding sales servers 20.
[0014] The download server 30 is a computer that manages an entity of the component. User environment E1 downloads the component entity from the download server 30, the component having been requested for purchase (purchased). License management server 10 is a computer that manages a license (use authorization) for the component that has been purchased.
[0015] In accordance with this embodiment of the present invention, the component is distributed by a unit called a sales package. Namely, each sales package is distributed separately. In addition, a set of multiple sales packages (that is, a combination of sales packages) can be a distribution unit as a set. In this embodiment of the present invention, the distribution unit having a set (combination) of several sales packages is called a "group".
[0016] Figure 2 shows an exemplary configuration of the sales package. As shown in figure 2, a sales package is provided as an archive file including a sales package information file and one or more function packages.
[0017] The sales package information file is a file that stores information about sales package attributes (sales package information).
[0018] Figure 3 shows an exemplary configuration of the sales package information. As shown in figure 3, the sales package information includes a product ID, a version, a name, a description, a supplier name, a distribution type and the like.
[0019] The product ID refers to an identifier (product identifier) exclusively allocated to each of the sales packages and a function package. The version refers to a version number of the sales package. The description is about the sales package. The supplier name is the name of the supplier (developer) of the sales package. The name refers to the name of the sales package (name of the sales package). The type of distribution refers to an item of information indicating whether activation (license authentication) is required. When activation is not required, the sales package can be used free of charge. In addition, the name, description and supplier name data is stored for each type of language using character codes corresponding to the type of language. Namely, the name, description and supplier name data are provided in many different languages in light of the worldwide distribution of sales packages.
[0020] Referring again to figure 2, the function pack is a software package packaged by the function. A function package is provided as an archive file (for example, JAR file (Java file (trademark)) including a function package information file and the entity of a component.
[0021] The function package information file refers to a file storing function package attribute information (function package information).
[0022] Figure 4 shows an exemplary configuration of the function pack information. As shown in figure 4, the function package information includes a product ID, a version, a name, a description, a supplier name, a distribution type, package dependency information and the like.
[0023] The product ID is for the function pack. The version refers to a version number of the function pack. The name refers to the role package name (role package name). The description is about the function package. The supplier name refers to the name of the supplier (developer) of the role package. The distribution type is an information item indicating whether activation is necessary. When activation is not required, the function pack can be used free of charge. Package dependency information refers to the product ID of another function package on which the function package (that function package) depends (is used). A role package can depend on several other role packages. Similar to sales package information, in relation to function package information, name data, description and supplier name data are stored for each type of language using character codes corresponding to the type of language.
[0024] In figure 2, a case is described where a group consists of three (3) sales packages. Even when a sales package belongs to a group, the sales package can be distributed (independently) separately.
[0025] Figure 5 shows an exemplary functional configuration of an equipment management system according to the first embodiment of the present invention. As shown in figure 5, sales server 20 includes a product registration section 21, a sales management section 22, a product master 23, and a product key transmission section 24.
[0026] Product registration section 21 downloads a list of information from the sales packages managed centrally to the license management server 10, and records product configuration information and similar input by an operator based on information list. In addition, product registration section 21 acts as a transmission medium for transmitting a registration request to register group configuration and similar information to the license management server 10. From user PC 50, section sales management 22 receives a purchase order to purchase a product having product information registered with product master 23. In addition, sales management section 22 issues a product key corresponding to the purchase order to the management server License key 10. Product key transmission section 24 transmits the product key issued to user's PC 50 as a response to the purchase order.
[0027] In this embodiment, the product refers to a concept including the sales package or the relevant license group and content. Due to this characteristic, even in the same sales packages, if the license content (license content) (for example, license type, license expiration date (valid period), and license volume number) differ, the same sales packages can be treated as different products. In the following, information on the license content is referred to as “license information”.
[0028] In addition, in the present invention, the product key refers to an identifier exclusively issued (or allocated) whenever the product is purchased. The product key is used as the information identifying the license (use authorization) for the sales package included in the product and is also used as the information verifying a product's entitlement buyer. In addition, in this embodiment, the product ID and the product key are explicitly distinguished from each other. Namely, the product ID is used when determining whether the sales package as the product is the same or different, and the product key is used to distinguish the act of purchasing the product. Therefore, whenever a product is purchased, different product keys are issued for the sales package having the same product ID.
[0029] The imaging apparatus 40 includes an installation section 421, a license update section 422, a package update section 423, a license check section 424, a deactivation section 425, a UI control 426, an installation information management table 427 and the like.
[0030] In response to the entry of the product key, installation section 421 controls a series of processes to install the sales package corresponding to the product key. For example, installation section 421 sends a request to license management server 10 so that license management server 10 determines the validity of the role package dependency relationship included in the sales package to be installed. In addition, installation section 421 downloads the sales package to be installed from download server 30, and acquires a license file 90 from license management server 10, license file 90 corresponding to sales package to be installed.
[0031] License file 90 is a file that stores the data certifying the license for the sales package (that is, the data to allow the use of the sales package). Namely, the sales package (component) according to that embodiment of the present invention cannot be used on the imaging apparatus 40 simply by acquiring the entity of the sales package (component). The sales package becomes usable when the license file 90 is inserted into the imaging apparatus 40.
[0032] License update section 422 controls a process (license update process) for updating (extending) the expiration date (valid period) of the license for the sales package having been installed on the imaging apparatus 40. Package update section 423 controls a process (sales package update process) for updating the version of the sales package having been installed on the imaging apparatus 40. License verification section 424 determines whether the use of the sales package can be used (continued) based on license file 90 when the sales package is to be used. The deactivation section 425 performs the deactivation of the sales package having been installed on the imaging apparatus 40. Specifically, for example, the deactivation section 425 deletes the sales package to be deactivated and the license file 90 corresponding to the package of sales. The control section of UI 426 performs, for example, display control of the operation panel of the imaging apparatus 40. The installation information management table 427 is a table managing information from the sales package having been installed on the apparatus. image 40 and is stored in a storage device of the image 40 apparatus.
[0033] License management server 10 includes an activation server section 11 and a component server section 15. Activation server section 11 includes a sales server cooperation section 111, an issuance section product key 112, a product key verification section 113, a license issue section 115, a deactivation section 116, a sales server authentication section 117, a sales site master 118, a sales package 119, a group ID master 120, a license management table 121, a group name master 122 and the like.
[0034] The sales server cooperation section 111 performs, for example, a process requested by the sales server 20, and a process corresponding to the information reported from the sales server 20. The product key issue section 112 generates the product key in response to the request from sales management section 22 of the sales server 20. In addition, the product key issue section 112 records the generated product key and the license information identified by the key of product in the license management table 121. The product key verification section 113 verifies the effectiveness of the product key entry on the imaging apparatus 40 based on the license management table 121 and similar after downloading the package and similar.
[0035] The license issue section 115 issues the license for the sales package. With the issuance of the license, the license management table 121 is updated and the license file 90 is generated. In response to the deactivation request from deactivation section 425 of the imaging apparatus 40, deactivation section 116 releases the license that is the target of the request. Sales server authentication section 117 authenticates sales server 20 using sales site master 118. Sales package master 119 records the sales package information list. The group ID master 120 records the membership information (i.e., group configuration information) between groups and sales packages. The group name master 122 records group names (group names). In addition, sales site master 118, sales package master 119, group ID master 120, license management table 121, and group name master 122 are stored on a management server storage device of license 10.
[0036] Component server 15 includes a dependency relationship determination section 151, an installation support section 152, a package update support section 153, a component management section 154, a management table component 155, a dependency relationship management table 156 and the like. The dependency relationship determination section 151 determines, for example, whether the function package, on which the function package included in the sales package to be installed or to be updated depends on, has already been installed on the imaging apparatus 40 More specifically, in response to a request from installation section 421 of the imaging apparatus 40, the dependency relationship determination section 151 determines whether the dependency relationship of the function package included in the sales package to be installed is resolved, for example, by the function pack having already installed on the imaging apparatus 40, as it refers to the component management table 155 and the dependency relationship management table 156. The installation support section 152 performs a process of supporting the installation of the sales package for the imaging apparatus 40. For example, the installation support section 152 generates HTML data (data list screen data installation) to display a screen so that the sales package to be installed can be selected, and provides the installation list screen data generated for installation section 421 of the imaging apparatus 40. The support section of package update 153 performs a process of supporting the update (update version) of the sales package on the image 40 apparatus. For example, the package update support section 153 generates HTML data (update list screen data) to display a screen so that the sales package to be updated can be selected, and provides the update list screen data generated for the update package 423 section of the imaging apparatus 40. The component management section 154 periodically purchases the sales package stored in the sales package management section 32 of the download server 30, and records the sales package configuration information and the dependency information for each function package included in sales package and similar in component management table 155 or dependency relationship management table 156. In addition, component management table 155 and dependency relationship management table 156 are stored on a license management server 10 storage device.
[0037] When each of the function packages has the information of its dependency destination and the license management server 10 records the dependency relationships between the function packages in the dependency relationship management table 156 based on the destination information dependency of function packages, it becomes possible to accurately record information on complicated dependency relationships. For example, when the role pack manufactured by the role pack manufacturer (or a sales pack including the role pack) is placed on the download server 30, license management server 10 acquires the dependency relationship between the packs function from the download server 30, and automatically records the dependency relationship between the function packages in the dependency relationship management table 156. So, for example, even when the sales site manager is different from the manufacturer of the function packs or similar, it may not be necessary for the sales site manager to recognize the dependency relationship between the function packs. As a result, for example, it may become possible to promote the manufacture of function packages by a third party supplier and increase the chances of sales.
[0038] Figure 6 shows an exemplary hardware configuration of the license management server 10 in accordance with that embodiment of the present invention. As shown in figure 6, the license management server 10 includes a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, and an interface device 105, which are connected together via of a B bus.
[0039] A process that performs processes performed by the license management server 10 is provided by using a recording medium 101 such as a CD-ROM. When recording media 101 storing the program is placed on drive device 100, the program is installed on auxiliary storage device 102 from recording media 101 via drive device 100. However, it is not always necessary to install the program using recording media 101. For example, the program can be downloaded from another computer over a network. Auxiliary storage device 102 stores not only the program, but also other necessary folders and data.
[0040] When an instruction to start the program is issued, memory device 103 reads the program from auxiliary storage device 102, and stores the program on memory device 103. CPU 104 performs functions (sections in figure 5 ) of license management server 10 based on running the program stored on memory device 103. Interface device 105 is used as an interface to connect to the network.
[0041] License management server 10 may further include a display device such as a liquid crystal display or a CRT display and an input device such as a keyboard and mouse.
[0042] In addition, the sales server 20, the download server 30, the user PC 50 and similar can have the hardware configuration similar to that in figure 6.
[0043] Figure 7 shows an exemplary hardware configuration of an image forming apparatus in accordance with that embodiment of the present invention. As shown in figure 7, the imaging apparatus 40 has hardware including a controller 41, a scanner 42, a printer 43, a modem 44, an operation panel 45, a network interface 46, an SD card partition 47 It's similar.
[0044] Controller 41 includes a CPU 411, a RAM 412, a ROM 413, an HDD 414 and the like. ROM 413 stores various programs and data to be used by the programs. RAM 412 is used as a storage area for loading a program and a working area for the loaded program and the like. CPU 411 performs several functions (each section shown in figure 5) for processing the program loaded in RAM 412. The HDD 414 stores a program and various data to be used by the program.
[0045] Scanner 42 is hardware to read image data from a manuscript. Printer 43 is hardware for printing image data on a printing sheet. Modem 44 is hardware to connect to a telephone line, and is used to transmit / receive image data in FAX communications. Operator panel 45 is hardware including an input medium like buttons for receiving input from a user and a display medium like a liquid crystal panel. The network interface 46 is hardware to connect to a network as a LAN (wireless or via a wired connection). The SD card partition 47 is used to read a program stored on an SD card 80. Namely, on the imaging device 40, not only a program stored on ROM 413, but also a program stored on SD card 80 can be loaded to run.
[0046] Next, a processing procedure performed on the equipment management system 1 according to the first embodiment of the present invention is described. Figure 8 is a sequence diagram illustrating a process for registering product information by the sales server 20. A product configuration to be sold can be determined for each sales area. The processes shown in figure 8 are performed when the configuration of the product to be sold is determined in a certain sales area.
[0047] For example, when a start registration instruction to register product information is entered on the sales server 20 by a manager on a sales site, the product registration section of the sales server 20 specifies the name of domain, a sales site ID, and a password stored on a storage device on sales server 20, and passes an authentication request to activation server section 11 of license management server 10 (step S11).
[0048] The sales server authentication section 117 having received the authentication request authenticates the sales server 20 based on the information specified in the authentication request and the sales site master 118.
[0049] Figure 9 shows an exemplary configuration of the sales site master 118. As shown in figure 9, the sales site master 118 records the domain name, sales site ID and password for each area of sales.
[0050] Sales server authentication section 117 authenticates sales server 210 by verifying (comparing) the domain name, sales site ID, and password in the authentication request and the domain name, ID sales site manager and password on sales site master 118. When authentication is successful, sales server authentication section 117 establishes a session and passes the session ID to sales management section 22 ( step S12). After that, communication between the sales management section 22 and the activation server section 11 is performed based on the session ID. When authentication is successful (that is, when the session ID is transmitted), product registration section 21 works to display a product information edit screen on the sales server display device 20 (step S13 ).
[0051] Figure 10 shows an example of the product information editing screen. Through the product information edit screen 210, the license package data can be entered as the domain name, the product ID, the type of product unit ID, the type of license, the expiration date of license (valid period), volume number, product type code, product name and the like.
[0052] For example, on the product information edit screen 210, when a selection button 2112 is clicked by a manager, the product registration section 21 transmits an acquisition request to acquire a list of sales sites for the sales server cooperation section 111 of activation server section 11 (step S14). In response to receiving the purchase request to purchase the list of sales sites, the sales server cooperation section 111 acquires a list of the sales sites and domain names from the sales site master 118, and transmits the list for product registration section 21 (step S15).
[0053] The product registration section 21 works to display the received list of domain names on the display device of the sales server 20 (step S16). When a domain name is selected from the list, the product registration section 21 works to display the selected domain name in a text box 2111 on the product information edit screen 210 (step S17).
[0054] Next, when a selection button 2114 is clicked by a manager, the product registration section 21 transmits an acquisition request to acquire the sales packages and a list of group information to the server cooperation section sales 111 of the activation server section 11 (step S18). In response to receiving the purchase request to purchase sales packages and the group information list, sales server cooperation section 111 acquires the sales package information list from sales package master 119, and additionally acquires the group information list from group ID master 120, group name master 122 and the like.
[0055] Figure 11 shows an exemplary configuration of the sales package master 119. As shown in figure 11, the sales package master 119 records the product ID, sales package name, seller name and the like for each sales package. The sales package name and salesperson name are registered for each type of language (such as Japanese and English). The information list transmitted in step S15 includes those items of information for each of the sales packages. However, only the sales package name and the salesperson name corresponding to a language environment of the sales server 20 can be transmitted. The language environment of the sales server 20 can be specified in the request in step S14 by the product registration section 21. Otherwise, based on a function of a communication protocol, the language environment of the sales server 20 can be determined. For example, in HTTP communications, a parameter indicating the language environment of the network browser is reported to the network server side. When such a communication protocol is used, the language environment of the sales server 20 can be determined based on such a parameter. Furthermore, it is assumed that the registration of the information in the sales package master 119 was performed, for example, by a manager of the license management server 10 in advance.
[0056] In addition, figure 12 shows an exemplary configuration of the group ID master 120. As shown in figure 12, for each combination of the group ID and the sales site ID, the group ID master 120 records group configuration information from the group ID, and a deletion flag. The reason that configuration and similar information is recorded for each combination of the group ID and sales site ID is that the group ID is uniquely assigned to each sales site. Like the group configuration information, the product ID of the sales package belonging to (included in) the group for each group ID of the group is recorded. The deletion flag is data indicating whether the group ID registered in the group ID master 120 can be deleted (ie, group deletion) or can be allowed. The data has a value of “ON” or “OFF”. The value of “ON” indicates that the deletion is possible or permissible. On the other hand, the value of “OFF” indicates that the deletion is not possible or not allowed (avoided). When a product related to a group is purchased, deletion of the group becomes impossible. Therefore, the initial value of the deletion flag is “ON”. This is because when a group is registered, there is no product purchased related to the group.
[0057] In addition, figure 12 shows a case where several records relevant to the same group ID (such as "001") are registered. This is because, in the group ID master in figure 12, a product ID from the sales package is recorded in a record. Namely, figure 12 shows a case where three sales packages belong to the group having the group ID “001”.
[0058] In addition, figure 13 shows an exemplary configuration of the group name master. As shown in figure 13, the group name master 122 registers group names for each type of language for each of the group Ids. Namely, the group name master 122 records the group names for each type of language for each of the groups.
[0059] Sales server cooperation section 111 extracts the group ID relevant to the sales site ID received during the authentication request (step S11) from the group ID master 120 among the group IDs registered in the group ID master 120. Then, the sales server cooperation section 111 generates information from group lists by acquiring the group name from the group name master 122, the group name corresponding to the extracted group ID . In addition, the group name included in the group list information can be limited to the group name corresponding to the language environment of the sales server 20.
[0060] Next, the sales server cooperation section 111 transmits the sales package list information and the group list information to the product registration section 21 (step S19). Product registration section 21 works to display a list screen of sales packages and groups (for example, a screen including sales package names and group names) on the sales server display device 20 with based on the list of information received from sales packages and groups (step S20). On the list screen, when any of the sales packages is selected, the product registration section 21 works to display the product ID and sales package name of the sales package selected in the 2113 text box and the text box. 2115, respectively, on the product information editing screen 210; in addition, product registration section 21 works to display the “product ID” in text box 2116 (step S21). The character string displayed in the 2116 text box indicates the product unit ID type of the ID displayed in the 2113 text box. The product unit ID type indicates which of the sales package product ID and group ID of the group is displayed in text box 2113. Namely, the product information edit screen 210 can be used to edit product information for the group. In this case, the group ID and group name are displayed in text box 2113 and text box 2115, respectively.
[0061] Next, on the product information editing screen 210, the rest of the product information is entered by the manager (step S22). Specifically, information items such as the license type, the license expiration date (valid period), the volume number, the product type code, the product name and the like are entered. The license type is information indicating that the product license is the sold license, temporary license, trial license or similar. The sold license can be used for an unlimited period after it is purchased. The temporary license can be used (is in effect) for a predetermined period only. The trial license is used for the purpose of using experience. The license type can be entered by selecting using the 2117 list box. The license expiration date (valid period) is an effective attribute when the temporary license or the trial license is selected as the license type, and indicates the period when the license is in effect. The license expiration date (valid period) is entered in text box 2118. The volume number refers to the license volume number. The volume license is granted to a user who has purchased a product with volume number two (2) or greater, so that the user is allowed to use the same sales package at the same time in the volume number range. The volume number is entered in the 2119 text box.
[0062] The product type code is an identifier to uniquely identify a product. The product type code is entered in the text box 2120. In addition, it is possible to define several products having different license contents (license information) for a single package or sales group. Therefore, the relationship between the sales package product ID or the group ID and the product type code is a one to many relationship. The product name is the name of the product. The product name is entered in the 2122 text box. Otherwise, when the 2121 button is clicked, based on the sales package name or group name, the license type, and the license expiration date (period valid), the product registration section 21 automatically generates the product name and displays the generated product name in text box 2122. In addition, on the product information edit screen 210, the product name in Japanese can be entered in the 2123 text box. The product name in other languages can be entered on another screen.
[0063] After the product information is entered on the product information edit screen 210, when the OK button 2131 is clicked, the product registration section 21 stores the input product information in the product master 23 (step S23 ).
[0064] Figure 14 shows an exemplary configuration of product master 23 on sales server 20. As shown in figure 14, product master 23 is a table managing information items including the product type code, product ID product unit (product ID or group ID), license type, license expiration date (valid period), volume number, product name and the like for each product.
[0065] When the product information is registered in the product master 23 of a sales server 20, it becomes possible to sell (distribute) the product in the sales area to which the sales server 20 belongs.
[0066] In the following, a generation process of generating a group (that is, a registration process of registering a group in the group ID master 120 and the group name master 122) is described. Figure 15 is a sequence diagram illustrating a procedure for processing a group generation process. The generation of a group (group generation) refers to the determination of the sales package included in a new group.
[0067] For example, when a group generation start instruction is entered on the sales server 20 by a sales site manager, the product registration section 21 of the sales server 20 functions to display an edit screen for group on the sales server display device 20 (step S31).
[0068] Figure 16 shows an example of the group edit screen 220. As shown in figure 16, in the group edit screen 220, it is possible to enter the group ID and the group name of the group to be generated (added ). The group ID is entered in area 221. The group name is entered in area 222.
[0069] In addition, in a table 223 of the group edit screen 220, it is possible to specify (determine) the sales packages to be included in the newly generated group (that is, it is possible to specify the combination of the sales packages included in the group). Specifically, when button 224 is clicked, a new line is added to table 223. In the example in figure 16, two lines are already added. Namely, in an initial condition, there are no lines (that is, the number of lines is zero (0)) in table 223. Then, when the selection button 225 of the added line is clicked (step S32), the section Product registration number 21 transmits an acquisition request to acquire the sales package information list for the sales server cooperation section 111 of the activation server section 11 (step S33). In response to receiving the purchase request to purchase the sales package information list, sales server cooperation section 111 acquires the sales package information list from sales package master 119. In addition, the sales server cooperation section 111 transmits the purchased list of sales package information to the product registration section 21.
[0070] Based on the received list of sales package information, product registration section 21 works to display a list of sales package lists (for example, a screen displaying the list of product Ids and the names of sales package) on the sales server display device 20 (step S35). On the list screen, when any of the sales packages is selected (step S36), the product registration section 21 works to display the product ID and sales package name of the selected sales package in the line to be currently operated (that is, the same line where the selection button 225 is clicked) in table 223. By doing this, in terms of the display, the sales package is added as a member (element) of the new group. In addition, steps S32 through S37 included in “loop 1” in figure 15 are repeatedly performed according to the number of sales packages to be added to the group. In addition, when any of the check buttons 226 of the lines added in table 223 is checked, and then the delete button 227 is clicked, the sales package on the line is deleted from the group in terms of the display.
[0071] After the sales package addition operation ends in table 223, when button 228 is clicked (step S38), product registration section 21 transmits a registration request to register the group for the cooperation section of sales server 111 (step S39). The registration request to register the group includes information items such as parameters, information items including group configuration information (that is, information items such as the group ID and the product ID of the sales package belonging to the group ) entry in the group edit screen 220 and items such as the domain name, sales site ID, password and the like stored on the storage device of the sales server 20. In response to the registration request to register the group, the sales server cooperation section 111 performs a group registration process (step S40). Specifically, for a new group, the configuration information is registered in the group ID master 120, and the group name is registered in the group name master 122. After performing the group registration process, the cooperation section Sales server 111 transmits the response indicating whether the registration process was successful for product registration section 21 (step S41).
[0072] Next, details of step S40 are described. Figure 17 shows a procedure for processing a group registration process.
[0073] As shown in figure 17, in step S40a, the sales server cooperation section 111 determines whether a required parameter is included in the group registration request received. Upon determining that the required parameter is included, sales server cooperation section 111 causes sales server authentication section 117 to authenticate sales server 20 (sales site) (step S40b). Sales server authentication section 117 authenticates sales server 20 by verifying the domain name, sales site ID and password in the group registration request and those in the sales site master 118.
[0074] When sales server 20 is authenticated, sales server cooperation section 111 determines whether the combination of the group ID and the sales site ID in the group registration request has already been registered in the group ID master group 120 (step s40c). When determining that the combination of the group ID and the sales site ID has not been registered, the sales server cooperation section 111 registers the records in the group ID master 120, the records including the group ID, the ID sales site number, product ID of the sales package, and similar in the group registration request (step S40d). The sales server cooperation section 111 sets the deletion flag to “ON”.
[0075] In addition, the sales server cooperation section 111 records the records in the group name master 122, the records including the group ID and the group name and the like included in the group registration request. In addition, in this embodiment, the group name registered when the group is generated is a group name in Japanese. Therefore, the language type for this record is “Japanese”.
[0076] Next, the sales server cooperation section 111 transmits a response to product registration section 21, the response indicating that the group registration was successful (step S40e). On the other hand, when determining that the required parameter is missing at step S40a, when authentication from sales server 20 failed at step S40b, or when determining that the combination of the group ID and the sales site ID has already been registered, the sales server cooperation section 111 transmits a response to product registration section 21, the response indicating that the group registration failed (step S40f).
[0077] As described above, in relation to a group, the group's configuration information (information associating the group with the sales package) is considered as the target to be managed; and the entity of the group itself (for example, a file including a set of sales packages belonging to group0 is not generated. Due to this characteristic, it may become possible to reduce the consumption (quantity) of the storage capacity used by generating the group .
[0078] In addition, when the product information of the generated group must be registered, a process as illustrated with reference to figure 8 can be performed on the group as a target (namely, by selecting the group in step S21).
[0079] As described above, the sales website can arbitrarily determine the configuration of the group. Therefore, it may become possible to more appropriately meet the needs of the market in the sales area and determine the configuration of the group that can be marketed to be effectively promoted.
[0080] Next, figure 18 is a sequence diagram illustrating a processing procedure when the product is sold. Sales server 20 in figure 18 is provided for the sales area to which the user's PC 50 in that figure belongs.
[0081] When a user in a certain E1 user environment enters the URL corresponding to a network page (product list page) displaying a list of products that can be purchased (to be purchased) via the PC's network browser 51 from user 50, web browser 51 transmits an acquisition request to acquire the product listing page for sales management section 22 of sales server 20 (step S121).
[0082] Next, the sales management section 22 generates the product list page based on product master 23 (step S122). Specifically, sales management section 22 generates HTML data such as the product list page displaying the product name, license type, license expiration date (valid period), volume number and the check button for each of the products registered in product master 22. Therefore, products related to a group license are formed (displayed) through the product information edit screen 210, and when a product's product information is registered in the master of product 23, the product related to the group license is also formed as an option on the product list page. In addition, the check button is used to select the product to be purchased. The sales management section 22 then transmits the generated product list page to web browser 51 (step S123). The web browser 51 displays the product list page received on the user's PC display device 50.
[0083] On the product list page, when a user selects a product button to buy the product, and presses the buy button, the web browser 51 transmits a purchase request including the product type code of the product to be purchased for sales management section 22 (step S124). Namely, the product list page is set so that the code for the selected product type is transmitted after the purchase button is pressed. In addition, on the product list page, several products can be selected. Therefore, in step S124, the purchase request can include several product type codes.
[0084] Next, sales management section 22 specifies the domain name, sales site ID and password, and transmits an authentication request to the activation server section 11 of the license management server 10 (step S125). Sales server authentication section 117 of activation server section 11 authenticates sales server 20 by checking (comparing) the domain name, sales site ID, and password in the authentication request with the name of domain, sales site ID, and password on sales site master 118. When determining that authentication is successful, sales server authentication section 117 establishes a session, and passes the session ID to sales management section 22 (step S126). After that, communications between the sales management section 22 and the activation server section 11 are performed based on the session ID.
[0085] Next, sales management section 22 acquires information items from product master 23, the information items being the product unit ID (product ID or group ID), the license type , the license expiration date (valid period), and the volume number that are registered corresponding to the product type code included in the purchase request. In addition, sales management section 22 broadcasts an issue request to issue the product key to product key issue section 112 of the activation server section 11 for specifying the purchased product unit ID (Product ID). product or group ID), the license type, the license expiration date (valid period) and the volume number (step S127). In addition, the issue request to issue the product key corresponds to a product purchase notice.
[0086] In response to the issue request to issue the product key, the product key issue section 112 generates the product key (step S128). The product key issue section 112 transmits the generated product key to sales management section 22 (step S129). In addition, when product keys for multiple products are requested to be issued, product keys for the respective products are generated. With respect to the product related to the group license, a single product key is generated for the product. By doing so, it may become possible to reduce the burden of managing product keys on the user side compared to a case where a product key is separately issued for each of the sales packages in a group.
[0087] After receiving the product key, the product key transmission section 24 of the sales server 20 transmits HTML data including the product key to the network browser 51 (step S130). The web browser 51 works to display the HTML data on the display device of the user's PC 50. By doing so, the user can recognize the product key issued when purchasing the product. In addition, the product key transmission section 24 can distribute the product key by sending an email describing the product key to the user's PC 50.
[0088] Below, details of step S128 are described. Figure 19 is a flow chart illustrating a procedure for processing a product key generation process by the product key issue section 112.
[0089] In step S141, the product key issue section 112 receives information items including the product unit ID (product ID or group ID), the license type, the license expiration date (period valid), and the volume number. Next, the product key issue section 112 determines whether the product unit ID received is the group ID (step S142). Specifically, the group ID corresponding to the product unit ID is searched in the group ID master 120. When the group ID corresponding to the product unit ID is searched (detected) (YES in step S142), the issuing product key 112 acquires all the product IDs associated with the group ID (that is, product IDs of the sales packages belonging to the group) from the group ID master 120 (step S143). Next, the product key issue section 112 sets the value of the deletion flags corresponding to the group ID in “OFF” (step S144). By doing this, deleting the group ID is avoided.
[0090] When negative determination is made in step S142 or after step S144, the product key issue section 112 generates records to record the product ID received or the product ID purchased from the group ID master 120 in the table license management 121 (step S145). Therefore, when multiple product IDs are acquired from group ID master 120, multiple records are generated. In addition, product key issue section 112 generates the number of record volumes for the same product ID. Therefore, when the volume value is two (2) or greater, two (2) or more records are generated for the same product ID.
[0091] Figure 20 shows an exemplary configuration of license management table 121. As shown in figure 20, license management table 121 includes information items such as a management number, product key, product ID , an equipment number, a status, the type of license, the license expiration date (valid period), a license issue date and the like for each license issued for the sales package.
[0092] Among these information items, such as the product ID, the license type, and the license expiration date (valid period), the values received in step S145 from the sales management section 22 are recorded. When multiple records are generated, the same values are recorded for each of the records generated. However, in the case of a group license (when the product ID of the sales package is acquired based on the group ID), the ID of each product purchased is recorded in each relevant generated record.
[0093] The management number refers to an identifier (number) uniquely allocated to each record after the record is generated for the license management table 121. Like the product key, the product key generated in a later step is registered. Like the equipment number, the equipment number of the imaging apparatus 40 is specified as the equipment to use the sales package when the license file 90 is issued. The equipment number refers to the identification information (equipment identifier) to uniquely identify each image training device 40. The status is an information item indicating the status of the license. In this embodiment, the license status includes "unlicensed", "in use" and "entry". “Unlicensed” is a status where a license is not issued. "In use" is a status where the license is being used. The “entry” is a status where the license is released (and is able to be used). Like the status, no value is recorded at step S145. The license expiration date (valid period) refers to an expiration date (valid period) of the license (license folder 90) calculated based on the license expiration date (valid period) when the license file 90 is issued . The license issue date refers to the license issue date (license folder 90) registered when license file 90 is issued.
[0094] Next, the product key issue section 112 generates a product key (step S146). The number of product keys to be generated is one (1) even when the product unit ID received in step S141 is a group ID or when the volume number is two (2) or more.
[0095] Figure 21 shows an exemplary configuration of the product key. As shown in figure 21, the product key is given including a unique ID, a product unit ID, a license type, a group license flag and the like.
[0096] The unique ID refers to a unique ID generated when the product key is generated. The exclusivity of the product key is ensured by the unique ID. The product unit ID refers to the product ID or group ID received in step S141, in other words, any of the product ID and group ID of any of the sales package or group of products purchased. The type of license refers to the type of license received in step S141. The group license flag refers to a parameter indicating whether the product unit ID in the product key is the group ID (true) or not (false). When determining that the product unit ID received is the group ID, the product key issue section 112 sets the group license flag to “true”.
[0097] Next, the product key issuance section 112 records the product key generated in the record generated in step S145, and updates the license management table 121 for adjusting the status in “entry” (step S147). When multiple records are generated in step S145 (that is, in the case of the group license or when the volume number is two (2) or more (in the case of the volume license)), the same product key is registered for each records.
[0098] In addition, in the license management table 121 in figure 20, the records having management numbers 1 to 3 correspond to the volume license. Volume license records have the same product key and product ID. On the other hand, the records having management numbers 4 and 5 correspond to the group license (group license). Group license records have the same product key. However, the group license records correspond to different sales packages. Therefore, the product IDs of the records are different from each other.
[0099] The product key generated as described above is transmitted to sales management section 22 of sales server 20 in step S129 in figure 18, and is additionally transmitted from sales management section 22 to the browser network 51 from user PC 50.
[0100] Next, the product sales package with the issued product key is installed.
[0101] Figure 22 is a sequence diagram illustrating a procedure for processing the installation of the sales package.
[0102] The user, having acquired the product key, enters the product key in the image forming apparatus where the sales package corresponding to the product key must be used (step S151). For example, the product key is entered through the function expansion adjustment menu screen described below to be displayed on the operation panel 45.
[0103] Figure 23 shows an example of displaying the function expansion adjustment menu screen. The function expansion adjustment menu screen 510 displays several menus to expand the functions of the imaging apparatus 40. In response to a predetermined input, the UI control section 426 controls to display the adjustment menu screen. function expansion 510 on the operation panel 45. On the function expansion menu adjustment screen 510, when a newly added menu 511 is selected, UI control section 426 controls to display a product key entry screen on the operation panel 45.
[0104] Figure 24 shows an example of displaying the product key entry screen. The product key entry screen 520 includes a product key entry line 521. In step S151, the product key is entered on the product key entry line 521.
[0105] After the product key is entered on product key entry line 521, when the next button 522 is selected, installation section 421 specifies the input product key and transmits a generation request to generate a screen of installation lists for the sales package related to the product key for installation support section 152 of component server section 15 (step S152).
[0106] Next, after receiving the generation request to generate an installation list screen, the installation support section 152 transmits a verification request to verify the effectiveness of the product key specified in the generation request to the verification of product key 113 from activation server section 11 (step S153). The product key verification section 113 determines (verifies) the effectiveness of the product key by referring to the license management table 121 (step S154). Specifically, the registration including the product key and having a status value other than “in use” is searched for in the license management table 121. When the registration is searched (detected), it is determined that the product key is in effect . On the other hand, when the record is not detected, it is determined that the product key is not valid. In this determination method, in a case where the product key is related to a group license product, when the license for at least part of the sales packages belonging to the group is not being used (but can be used), it is determined that the product key is in effect.
[0107] When determining that the product key is in effect, product key verification section 113 transmits the product ID associated with the product key in the license management table 121 (that is, the product ID of the package sales) for installation support section 152 (step S155). Therefore, in terms of the product key related to the group license or the volume license, several product Ids are transmitted. In addition, in the case of the product license, an information item is transmitted to the installation support section 152, the information item indicating whether the license for each product ID (for each sales package belonging to the group) is used . This is because, in the case of the group license, some of the sales packages belonging to the group may not be used; therefore, it becomes possible to distinguish the license (sales package) that is being used from the license (sales package) that is not being used.
[0108] On the other hand, when determining that the product key to be determined is not in effect (invalid), the installation support section 152 transmits error screen data to display an error message indicating that the product key is invalid for installation section 421. In response to receiving error screen data, installation section 421 causes UI control section 426 to control the display of an error message based on the screen data of mistake.
[0109] Figure 25 shows an example of displaying the error screen when the product key is invalid. Error screen 530 displays a product key error message (indicating that the product key is invalid) and a product key entry line 531 and the like. The user can enter the correct product key in the product key entry line 531. When the correct product key is entered in the product key entry line 531, and the OK button 532 is selected, the procedure from step S152 is executed again. On the other hand, when the cancel 533 button is selected, the installation of the sales package is canceled (aborted).
[0110] In step S155, after receiving the determination result indicating that the product key is determined to be in effect, as it refers to a component management table 155, the installation support section 152 generates screen data from installation list for the sales package corresponding to the product ID transmitted from the product key verification section 113 (step S156).
[0111] Figure 26 shows an exemplary configuration of the component management table. As shown in figure 26, component management table 155 records the product ID, version, name, description, vendor name, a distribution type, a download path, the product package ID and similar function for each sales package. The version refers to the version of the sales package. The name refers to the name of the sales package. The description refers to the description of the sales package. The vendor name refers to the vendor name of the sales package. The distribution type refers to the distribution type of the sales package. The download path refers to the sales package position information in the sales package management section 32 of the download server 30. In this embodiment, like the position information, the URL (Uniform Resource Locator) is used. The role package product ID is the list of the role package product ID that belongs to the sales package.
[0112] In addition, the contents of the component management table 155 are recorded by periodically purchasing the sales package from the download server 30 by the component management section 154 and by analyzing the contents of the sales package. Specifically, such as the product ID information items, version, name, description, supplier name, and distribution type, the product ID information items, version, name description, supplier name and distribution type that are recorded in the sales package information file stored in the sales package are recorded. Therefore, the information items of the name, description and name of the supplier are registered for each type of language. Like the product ID of the function package, the product ID registered in the function package information file stored in each of the function packages included in the sales package is registered. In addition, the download path is reported from the download server 30 when the sales package is purchased.
[0113] Next, the installation support section 152 transmits the generated installation list screen data to the installation section 421 of the imaging apparatus 40 (step S157). Installation section 421 enters the installation list screen data received in UI control section 426. UI control section 426 controls to display the installation list screen on operator panel 45 based on the screen data installation list (step S158).
[0114] Figure 27 shows an example of displaying the installation list screen. The installation list screen 540 displays a list of installation target sales packages (installation candidates) and the check box is arranged to select whether installation of the corresponding sales package is required (that is, use of the installation package). sales is required). The user selects the check box for the sales package to be installed. In the example in figure 27, packages 1 through 4 are listed as candidates for installation, and packages 1 through 3 are selected as installation destinations.
[0115] Furthermore, as is obvious from the processing procedure described above, when the product key of the product related to the group license is entered on the 520 product key entry screen, a list of the sales packages belonging to the group related to the group license is displayed on the installation list screen 540. Therefore, a user can selectively define some of the sales packages that belong to the group as the installation targets. In other words, it is possible to temporarily remove an unnecessary sales package that belongs to the group so that it is not defined as the installation target. By selectively installing the sales packages that belong to the group, it may become possible to flexibly meet the user's requirements in the group license products. Needless to say, it is possible to define all sales packages that belong to the group as the installation targets.
[0116] In addition, on the installation list screen 540, the name of the sales package is displayed according to the language environment of the imaging apparatus 40. Namely, after the generation of the data from the list screen the installation support section 152 uses the name of the registered sales package based on the language type corresponding to the language environment of the imaging device 40. The language environment of the imaging device 40 is determined with based on information indicating the language environment of the imaging apparatus 40, the information being included in the generation request to generate the installation list screen data transmitted from the imaging apparatus in step S152. In addition, this feature that the sales package name is displayed in a language type corresponding to the language environment of the imaging apparatus 40 is also applied to (supported in) several screens described below.
[0117] On the installation list screen 540, when the check box for the sales package to be installed is selected and the install button 541 is selected (S159), installation section 421 specifies the product ID of the sales package marked (as an installation destination) on the installation list screen 540 and the configuration information for all sales packages having been installed on the image 40 apparatus, and transmits an installation request to install the sales package to be installed for installation support section 152 of component server section 15 (step S160).
[0118] In addition, the product ID of the sales package marked on the installation list screen 540 is acquired from the installation list screen data. In addition, the configuration information of all sales packages having been installed on the imaging apparatus 40 is acquired from the installation information management table 427.
[0119] Figure 28 shows an exemplary configuration of the installation information management table. As shown in figure 28, the installation information management table 427 records information items such as the product ID, the version, the function package product ID, an activation flag, the license expiration date (period valid) and similar for each sales package having been installed on the image training device 40.
[0120] The function package product ID is a list of the product IDs of the function packages that belong to the sales package. The activation flag indicates whether the sales package is activated (that is, if the activation was performed on the sales package). The license expiration date (valid period) is the expiration date (valid period) of the license issued for the sales package (for example, license file expiration date 90). In addition, the activation flag and license expiration date (valid period) of the function package are the same as the activation flag and license expiration date (valid period), respectively, of the sales package to which the package of function belongs. In addition, the contents of the installation information management table 427 are recorded after installing the sales package described below.
[0121] The configuration information transmitted in step S160 includes all information items having been recorded in the installation information management table 427.
[0122] Next, the installation support section 152 causes the dependency relationship determination section 151 to perform the sales package dependency check related to the product ID included in the installation request (step S161) . Specifically, the dependency relationship determination section 151 determines whether the function package on which the function package included in the sales package related to the product ID depends (that is, whether the function package used by the function package included in the sales package related to the product ID), has already been installed on the imaging device 40.
[0123] The installation support section 152 then generates the HTML data (confirmation screen data) to display a confirmation screen according to the result of checking the dependency relationship (confirmation screen) (step S162) , and transmits the confirmation screen data to installation section 421 (step S163). The details of steps S161 and S162 are described below.
[0124] Next, installation section 421 enters the confirmation screen data received in the control section UI 426. The control section of UI 426 controls to display the confirmation screen on the operation panel 45 based on the data of confirmation screen (step S164).
[0125] Figure 29 shows an example of displaying the confirmation screen in a case where there is no problem (detected) in the dependency relationship. As shown in figure 29, confirmation screen 550a indicates that there is no problem with the dependency relationship for the sales package (package 1) selected as an installation destination. Specifically, area 552a indicates that a sales package (trusted package) on which package 1 depends is selected as an installation destination or has already been installed on the imaging apparatus 40.
[0126] On confirmation screen 550a, when OK button 551a is selected (step S165), installation section 421 specifies the URL corresponding to each sales package having been defined as the installation destination, and transmits a download request to download each of the sales packages to the download processing section 31 from the download server 30 (step S166). Namely, the URL corresponding to each sales package and the download request transmission instruction are associated with the OK button 551a.
[0127] In addition, figure 30 shows an example of displaying the confirmation screen in a case where the trusted package is capable of being installed simultaneously. As shown in figure 30, among the trusted packages related to the sales package selected as the installation destinations, area 552b of the confirmation screen 550a indicates a trusted package is capable of being installed simultaneously, the trusted package not being installed on the image formation 40 and not defined as the installation target, and also indicates whether it is necessary to install the trusted package simultaneously. In this case, the fact that it is possible to perform the simultaneous installation is determined based on the distribution type of the trusted package.
[0128] When OK button 551b on confirmation screen 550b is then selected (step S165), installation section 421 specifies the URL of each of the sales packages defined as the installation destinations and the URL of the sales package (package to be installed simultaneously, and transmit the download request to download the sales packages to the download processing section 31 of the download server 30 (step S166). Namely, the sales package URL defined as the installation destination, the sales package URL (trusted package) to be installed simultaneously, and the download request transmission instruction are associated with the OK button 551b.
[0129] In addition, figure 31 shows an example of displaying the confirmation screen in a case where the trusted package cannot be installed simultaneously. As shown in figure 31, area 552c on confirmation screen 550c indicates that there are three (3) sales packages that cannot be installed. In terms of those three (3) sales packages, more details are described in areas 553c, 554c and 555c. Area 553c indicates that the dependency (relation) of package 3 cannot be canceled (dissolved) (the dependency package cannot be installed simultaneously). Area 554c indicates that package 4 license has already been purchased (used). Area 555c indicates that package 5 cannot be installed simultaneously with the other packages (packages 1 and 2 in the case of figure 31) defined as the installation destinations. In addition, figure 31 shows a case where packages 1 through 5 are selected as the installation destinations.
[0130] When the OK button 551c on the 550c confirmation screen is then selected (step S165), installation section 421 specifies the URL of each of the installable sales packages, and transmits a download request to download each of the sales packages for download processing section 31 from download server 30 (step S166). Namely, the URL of each installable sales package and the download request transmission instruction are associated with the OK button 551c.
[0131] In response to the download request in step S166, download processing section 31 acquires the sales package from the sales package management section 32, the sales package being identified by the URL specified in the download request , and transmits the sales package to installation section 421 (step S167). Installation section 421 stores the sales package received in a temporary storage area (for example, a temporary file) on the HDD 414.
[0132] When the download of the sales package ends, installation section 421 specifies the product key entry in step S151, the product ID of the sales package defined as the installation destination, and the equipment number of the device image format 40 registered in ROM 413 or HDD 414, and transmits a generation request to generate license file 90 (a use request to use the license) to license issue section 115 of the activation server section 11 (step S168). Next, license issue section 115 generates license file 90 based on the product key and license management table 121 (step S169).
[0133] Figure 32 shows an exemplary configuration of the license file 90. As shown in figure 32, the license file 90 includes items of product ID information, the equipment number, and the expiration date (valid period) . The product ID refers to the product ID of the sales package to which the license is granted (sales package set usable by the license) by the license file 90. The equipment number refers to the equipment number of the training device image 40 in which the use of the sales package related to the product ID is permitted by the license file 90. The expiration date (valid period) refers to the expiration date (valid period) of the license granted by the license file 90 .
[0134] Like the product ID of the license file 90, the product ID related to the product key included in the generation request to generate the license file 90 is registered. In this case, when the product key is related to the group license, that is, when the various different product IDs for the product key are registered in the license management table 121, the license issue section 115 generates the file license number 90 for each of the sales packages. Therefore, even in the case of a group license, such as the product ID of the license file 90, the product ID of the sales package is registered.
[0135] As the equipment number in the license file 90, the equipment number included in the generation request to generate the license file 90 is registered. When the license file expiration date 90, the date (for example, year / month / day) obtained by adding the expiration date (valid period) to the current date is recorded, the expiration date being recorded in the management table number 121 corresponding to the product key and the product ID included in the generation request to generate the license file 90.
[0136] The license issue section 115 then transmits the generated license file 90 to installation section 421 (step S170). Installation section 421 stores the received license file 90 in a temporary storage area (for example, a temporary file) on the HDD 141.
[0137] After receiving license file 90, installation section 421 performs a sales package installation process (step S171). Details of the installation process are described below.
[0138] In addition, in the description above, an example is described where an acquisition request to purchase the sales package is transmitted to the imaging apparatus 40 using the installation list screen data in step S157 or the data confirmation screen in step S163. However, at that time, the sales package itself (that is, the main body of the program) can be transmitted to the image forming apparatus 40. For this purpose, component server 15 can download the sales package a be installed from the download server 30, and transfer the sales package to the image training device 40.
[0139] In addition, when some of the sales packages that belong to the group are installed (that is, when some of the sales packages that belong to the group are selected on the installation list screen 540), the rest of the sales packages that belong to the group can be separately installed. When the rest of the sales packages are to be installed, the user can operate to display the 520 product key entry screen, and enter the group product key again. In this case, the installation support section 152 generates the installation list screen data in such a way that the checkbox is not provided for the sales package being used by the license issued between the sales packages that belong to the group. Therefore, the installation list screen 540 is displayed in which the sales package being used by the issued license cannot be selected as the installation destination. The information indicating whether the sales package license is in use is determined based on the information that is transmitted by the product key verification section 113 in step S155 and that indicates whether the license is in use for each product ID it belongs to to the group.
[0140] Below, details are described of the processes performed in steps S161 and S162 of figure 22 by the component server section 15 of the license management server 10.
[0141] Figure 33 is a flow chart illustrating a procedure for processing the verification process of verifying the dependency relationship and a process for generating the confirmation screen data by the component server section 15.
[0142] In step S175, the dependency relationship determination section 151 defines a product ID (ie sales package) as a target to be processed, the product ID being selected from the product Ids received in the request checklist to check the dependency relationship in step S160 in figure 22. Next, the dependency relationship determination section 151 determines whether the sales package to be processed (hereinafter referred to as “current sales package”) has already been activated based on the activation flag included in the configuration information for the current sales package among the configuration information items received for each of the sales packages in step S160 (step S176). When determining that activation has not been performed (NOT in step S176), the dependent relationship determination section 151 determines whether there is a sales package (trust package) on which the current sales package depends based on the component management table 155 (see figure 28) and a dependency relationship management table 156 (step S177).
[0143] Figure 34 shows an exemplary configuration of the dependency relationship management table. As shown in figure 34, the dependency relationship management table 156 records items of function package product ID information and the product ID of trusted function packages. In this table, a plurality of the product ID of trusted function packs can be registered. In addition, the number “0” in figure 34 indicates that there is no function pack on which the function pack depends.
[0144] Similar to component management table 155, the contents of the dependency relationship management table 156 are recorded by analyzing the contents of the sales package periodically acquired by component management section 154. Specifically, the contents of the package dependencies recorded in the function package information file for each of the function packages in the sales package are stored in dependency relationship management table 156 as the product ID of trusted function packages.
[0145] In step S177, the dependent relationship determination section 151 acquires a list of the function package product ID registered for the current sales package product ID in component management table 155. Next, the section dependent relationship determination method 151 specifies another function package (hereinafter referred to as “trusted function package”) on which the function package depends based on the product ID of the acquired function package and the dependency relationship management table 156. In determining that there is a trust function package, the dependency management table 156 specifies the sales package that the trust function package belongs to by referring inversely to the dependency management table 156. The package specified sales package is the trusted package of the current sales package. In addition, there may be several trusted packages. In addition, the search for the dependency relationship between function packages is performed recursively.
[0146] When determining that there is no trust package (NOT in step S177), the dependent relationship determination section 151 associates and records the information indicating that there is no dependency relationship in the current sales package with the product ID of the current sales on memory device 103 (step S178). On the other hand, when determining that there is a trust package (YES in step S177), the dependent relationship determination section 151 determines whether the trust package has already been installed or is defined as the installation destination based on the configuration information received for each sales package in step S160 or the product ID of the sales package to be installed received in step S160 (step S179). Namely, when the configuration information corresponding to the trust package is received, it is determined that the trust package has already been installed on the imaging apparatus 40. In addition, when the product ID of the trust package is included in the product ID a installed, it is determined that the trusted package is defined for the installation target.
[0147] When the trust package has already been installed (YES in step S179), the dependent relationship determination section 151 determines whether the trust package has already been activated (enabled (that is, if the trust package is in a status where the trust package is usable) based on the configuration information received for each sales package (step S180), in which case, based on the activation flag included in the configuration information corresponding to the trust package, it is determined whether the trust package has already been activated .
[0148] When determining that the trusted package has already been activated or that the trusted package is defined as the installation target (YES in step S180), the dependent relationship determination section 151 associates and records (stores) the information indicating that it does not there is a problem in the relationship dependent on the current sales package with the production ID of the current sales package on memory device 103 (step S178). When determining that there is a trusted package that has not been activated (NOT in step S180), the dependent relationship determination section 151 associates and records (stores) the information indicating that it is necessary to perform activation of the trusted package with the package production ID sales volume on memory device 103 (step S181).
[0149] In addition, when determining that there is a trust package that is not installed (NOT in step S179), the dependent relationship determination section 151 determines whether it is possible to simultaneously install the trust package based on the component management table 155 (step S182). Namely, in component management table 155, when the distribution type corresponding to the product ID of the trust package indicates that it is not necessary to perform activation, it is determined that the trust package can be installed simultaneously. On the other hand, when the distribution type corresponding to the trust package's product ID indicates that activation is required, it is determined that the trust package cannot be installed simultaneously.
[0150] When determining that there is a trust package that can be installed simultaneously (YES in step S182), the dependent relationship determination section 151 associates and registers the product ID of the trust package as the product ID of the trust package that can simultaneously be installed with the product ID of the sales package on the memory device 103 (step S183). When determining that there is a trust package that cannot be installed simultaneously (NOT in step S182), the dependent relationship determination section 151 associates and registers the product ID of the trust package as the product ID of the trust package that cannot be simultaneously installed with the product ID of the sales package on the memory device 103 (step S18 4).
[0151] In addition, when determining that the current sales package has been activated (YES in step S176), the dependent relationship determination section 151 associates and records the information indicating that the license has already been purchased with the product ID of the package sales volume on memory device 103 (step S185).
[0152] When the execution of the processes in steps S175 to S185 was completed in each of the product Ids received in the verification request to verify the dependency relationship in step S160 of figure 22 (YES in step 186), the support section of installation 152 generates the confirmation screen data based on the information stored in the memory device 103 (step S187). For example, when there is no problem for all sales packages, the confirmation screen data is generated in order to display confirmation screen 550a as shown in figure 29. In addition, when the information as in step S183 is recorded, the confirmation screen data is generated in order to display confirmation screen 550b as shown in figure 30. In addition, when the information as in step S181, S184 or S185 is recorded, the confirmation screen data is generated in a way to display confirmation screen 550c as shown in figure 31.
[0153] In addition, in each confirmation screen data, the URL of the installable sales package is associated with the OK button. The installable sales package URL is purchased from the download path of component management table 155.
[0154] In the description above, a case is described where the trusted package is indicated (provided) for each sales package. However, the trusted package can be indicated (provided) for each function package. Furthermore, in this embodiment, even in a case where the trusted package is indicated (provided) for each function package, since the sales package is assumed to be treated as the distribution unit, which should be treated as the installation target is the sales package that includes the function package.
[0155] Below, details are described of the processes in steps S168 through S170 of figure 22 performed by the activation server section 11 of the license management server 10 are described. Figure 35 is a flowchart illustrating a procedure for processing a generation process of generating the license file through the activation server section 11. In addition, in Figure 35, a case is described assuming that a product key is treated as a processing target. Therefore, when multiple product keys are received, processes from steps S192 are performed for each of the product keys.
[0156] In step S191, license issue section 115 receives information items for the product key, product ID and equipment number from installation section 421 of the imaging apparatus 40. Next, the section License issue number 115 determines whether the product key license is usable. Specifically, the license issue section 115 determines whether the product key received is recorded in the license management table 121 (step S192). When determined that the product key is registered (YES in step S192), the license issue section 115 determines whether the equipment number equal to the equipment number received is registered in the license management table 121 as the corresponding equipment number to the product key (step S193). When determining that the same equipment number is not registered (NOT in step S193), the license issue section 115 determines whether there is a record having an “entry” status between the records that corresponds to the product key and the product ID received in license management table 121 (step S194). When determining that there is such a record (hereinafter referred to as the “destination record”) (YES in step S194), the license issue section 115 records the number of equipment received in the destination record, and adjusts (changes) the status from the target record to “in use” (step S196). Namely, information indicating that the license corresponding to the product key is being used is recorded. In addition, when the “license expiration date (valid date)” information item is recorded in the destination record (that is, when the destination record is the record corresponding to the temporary license), the license issue section 115 calculates a date by adding the license expiration date (valid period) to the current date, and records the calculated date (valid period) in the destination record as the license expiration date (valid period).
[0157] Next, the license issue section 115 generates the license file 90 (see figure 32) including the product ID information items, equipment number and license expiration date (valid period) in the registry destination (step S197). In addition, in this case, the license file 90 is generated for each record in the license management table 121, that is, for each license corresponding to the sales package. The license issue section 115 then transmits the generated license file 90 to the installation section 421 of the imaging apparatus 40 (step S198).
[0158] On the other hand, when determining that there is a record recording the equipment number equal to the equipment number received corresponding to the product key (YES in step S193), the license issue section 115 determines whether the registration status is “Entry” (step S195). When determining that the status is “input” (YES in step S195), the processes after step S196 are executed.
[0159] In addition, when determining that there is no record corresponding to the product key (NOT in step S192), when determining that there is a record having the status “entered” in the license management table 121 among the records corresponding to the product and the product ID received (NOT in step S194), or when determining that the registration status is not “input”, the record recording the equipment number equal to the equipment number received for the product key (NOT in the step S195), license issue section 115 assumes that an error is detected, and does not generate license file 90; that is, the license issue section 115 does not issue the license.
[0160] Below, details of the calculation process for calculating the license expiration date (valid period) performed in step S193 are described. Figure 37 is a flow chart illustrating the calculation process for calculating the license expiration date (valid period).
[0161] Firstly, in step S196a, the license issue section 115 determines whether the type of license registered in the destination record is any between the temporary license and the test license, that is, if the license has an expiration date (valid period). When determining that the license type is neither the temporary license nor the test license (NOT in step S196a), the license issue section 115 does not calculate the license expiration date.
[0162] On the other hand, when determining that the license type is the temporary license or the test license (YES in step S196a), the license issue section 151 determines whether the destination record is related to the group license ( step S196b). Specifically, the license issue section 115 searches for the other record having a product ID different from the product ID of the destination record and having a product key equal to the product key of the destination record. When the corresponding record is searched (detected), it is determined that the target records are related to the group license. On the other hand, when the corresponding product key is not detected, it is determined that the destination record is not related to the group license.
[0163] When determining that the target record is related to the group license (YES in step S196b), the license issue section 115 determines whether there is a record that belongs to the same group as the target record group and that the license is in use (step S196c). Specifically, among the other record sought in step S196b, it is determined that there is the record having the status "in use". When determining that there is a corresponding record (YES in step S196c), the license issue section 115 records the date calculated by adding the license expiration date (valid period) to the license issue date of the registration to the expiration date of license (valid period) of the destination record (step S196d). Namely, the license expiration date (valid period) of the sales packages that belong to the same group becomes identical.
[0164] On the other hand, when determining that the destination record is not related to the group license (NOT in step S1965b), the license issue section 115 determines whether the destination record is related to the volume license 9stage S196e) . Specifically, the license issue section 115 searches for the other record having the product ID equal to the product ID of the destination record and having the product key equal to the product key of the destination record. When determining that the corresponding record is searched (detected), it is determined that the destination record is related to the volume license. On the other hand, when determining that the corresponding record is not detected, it is determined that the destination record is not related to the volume license.
[0165] When determining that the destination record is related to the volume license (YES in step S196e), the license issue section 115 determines whether the use of the volume license has already started (step S196f). Specifically, it is determined whether there is a record having the status "in use" among the records searched (detected) in step S196e. when determining that there is the corresponding record (YES in step S196e), the license issue section 115 calculates a date by adding the license expiration date (valid period) of the destination record to the license issue date of the record, and records the date calculated on the license expiration date of the destination record (S196g). Namely, the license expiration date (valid period) of all licenses that belong to the volume license becomes identical.
[0166] In addition, when determining that the destination record is related to the group license and that the group related license has not been used (NOT in step S196c), when the destination record is not related to the group license or the volume license (NOT in step S196e), or when determining that the destination record is related to the volume license and that the use of the group related license has not started (NOT in step S196f), the license issue section 115 calculates a date obtained by adding the license expiration date (valid period) to today's date, and records the date calculated on the license expiration date (valid period) of the destination record (step S196h).
[0167] Next, details of the process of step S171 of figure 22 performed by the image forming apparatus 40 are described. Fig. 36 is a flow chart illustrating a processing procedure for installing the sales package performed by the imaging apparatus 40.
[0168] In step S211, installation section 421 records the information included in each sales package stored in the temporary storage area and the information included in each license file 90 in the installation information management table 427. Namely, the product ID and version registered in the sales package information file included in the sales package are registered in the product ID and version, respectively, registered in the installation information management table 427. As the product ID of the package function, the product ID registered in the function package information file stored in each function package included in the sales package is registered. In addition, the value indicating that the activation has already been performed is recorded in the activation flag. In addition, as the license expiration date (valid period), the expiration date (valid period) recorded in the license file 50 is recorded.
[0169] Next, installation section 421 defines the status of the sales package in usable for storing the license file 90 and the sales package in a predetermined storage area (folder), the license file 90 and the package sales have been stored in the temporary storage area.
[0170] In addition, the license file 90 is used during the license check performed by the license check section 424 when the function package included in the sales package is started. Namely, the license verification section 424 allows the function package to start when the following conditions are met: there is a license file 90 corresponding to the sales package to which the function package to be started belongs to; the number of equipment in the license file 90 is the same as that of the imaging device 40 on which the function package is to be started; and the expiration date (valid period) of the license file 90 has not expired. Otherwise, starting the function pack is not allowed. In addition, license verification section 424 can perform license verification based on component management table 425.
[0171] On the other hand, a charge for the installed sales package is made, for example, by the sales management section 22 of the sales server 20 based on information from the license management table 121 periodically acquired by the server section of the sales server. activation 11. More specifically, when there is a record in the license management table 121 that the license issue date is after the most recent billing date, the billing (operation) is made for the license corresponding to the record.
[0172] As described above, according to the first embodiment of the present invention, a user can easily perform a series of operations such as downloading, activating and installing the sales package by operating the screens sequentially required in the guided image formation apparatus 40 by the activation server section 11 or the component server section 15 of the license management server 10.
[0173] In addition, the dependency relationship related to the sales package selected as the installation destination is automatically verified, and the trusted package is also automatically included (defined) as the installation destination. Therefore, it can become possible for a user to easily install without fear of complicated dependency relationships between sales packages.
[0174] In addition, for one side of product sales (E2 manufacturer environment), it may become possible to properly manage the usage status of sales packages by users. Specifically, based on the information in the license management table 121, it may become possible to understand (manage) which of the sales packages is being used based on the type of license type for each of the imaging devices 40 (numbers of equipment). So, for example, when a bug is detected in a sales package or when a sales package is updated (for version update), it may become possible to specify the imaging device using the sales package, thereby allowing provide appropriate and similar service.
[0175] In addition, the license expiration date is not determined when the product is purchased (that is, when the purchase order is sent to the sales server 20) but determined when the sales package is installed (ie , when the license starts). Therefore, it may become possible to ensure flexibility in handling the license. Namely, a user can install at any convenient timing after purchasing the product. Even in such a case, the user may not suffer a loss in terms of the license expiration date (valid period).
[0176] In addition, in the product related to the group license, the product key is issued for each of the products. Therefore, a user can, for example, install all sales packages that belong to the product. As a result, it may become easier, for example, to install the sales packages that belong to the group.
[0177] Next, the license update process is described. In a case of the temporary license, when a user uses a product related to the temporary license, the user can extend the license expiration date (valid period) of the product by performing the license update process.
[0178] Figure 38 is a sequence diagram illustrating a procedure for processing the license update process.
[0179] In case of updating the license, while the function expansion menu definition screen 510 (see figure 23) is displayed on the operation panel 45, the expansion function management menu 513 is selected by the user . In response to the 513 expansion function management menu selection, UI control section 426 controls to display an expansion function management screen on the operation panel 45.
[0180] Figure 39 shows an example of displaying the expansion function management screen. As shown in figure 39, the expansion function management screen 560 includes a sales package list display area 561. In the sales package list display area 561, a list of sales packages installed on the image formation 40 is displayed. In this list, a check button is provided for each of the sales packages. When the check mark button for the sales package corresponding to the license to be updated is checked and the purchase / update license button 562 is selected by a user, the UI control section 426 controls to display a purchase / update license screen on the operation panel 45.
[0181] Figure 40 shows an example of displaying the purchase / update license screen. As shown in figure 40, the purchase / update license 570 screen includes a product key entry line 572 for the product key corresponding to the sales package marked on the expansion function management screen 560. When the product key is entered in the product key entry line 572 and the OK button 571 is selected by the user (step S301), the update license section 422 specifies the input product key, the product ID of the sales package corresponding to the license to be updated, and the equipment number of the imaging device 40 registered in ROM 413 or HDD 414, and transmits a license update request (a generation request to generate a new license file) to the issuing section license 115 of activation server section 11 (step S302).
[0182] In response to receiving the license update request, license issue section 115 updates license management table 121 (step S303). Specifically, when the registration license type corresponding to the product key, the product ID and the equipment number specified in the update request is a temporary license, the license issue section 115 updates the license expiration date (period valid) and the registration license issue date. In addition, when the registration status is “inbound”, the license issue section 115 updates the status by setting the status to “in use”. In this case, as the new license expiration date (updated) (valid period), the date determined by adding the valid license period of the registration to the license expiration date (valid period) registered until the present or the current date. that comes later, is provided. In addition, the new license issue date (updated) is set for the current day in year / month / day format. In addition, when multiple product IDs are specified, the update is performed on each of the various records.
[0183] Next, the license issue section 115 generates the license file 90 (see figure 320 including the product ID information items, the equipment number, the expiration date (valid period) registered in the registry , for each of the updated records in the license management table 121 (that is, for each of the sales packages defined to be updated) (step S304).
[0184] Next, the license issue section 115 transmits the generated license file 90 to the license update section 422 (step S305). License update section 422 deletes the existing license file 90 from the sales package corresponding to the license to be updated, and stores the received license file 90 in a predetermined storage area on the HDD 414 (step S306). In addition, the license update section 422 updates the installation information management table 427 based on the license file received 90. Specifically, the expiration date (valid period) of the registration corresponding to the product ID registered in the license file. license 90 is updated with the expiration date (valid period) recorded in the license file 90. In addition, license update section 422 sets the registration activation flag value to the value indicating that the activation has already been performed.
[0185] By performing the above processes, the user can use the same sales package until the new (updated) expiration date.
[0186] In addition, the charge for updating the license is made after installation. Namely, billing is done by sales management section 22 of sales server 20 based on information from the license management table 121 periodically acquired by activation server section 11. More specifically, when there is a record having the date license issue date after the most recent charge date in the license management table 121, the charge is made for the license related to the registration.
[0187] Next, the sales package update process (sales package update process) is described. As long as the license is valid, the user can update the sales package with an updated version.
[0188] Figure 41 is a sequence diagram illustrating a processing procedure for the sales package update process. As shown in figure 41, while function expansion menu definition screen 510 is displayed on operator panel 45, when update menu 512 is selected (step S401), package update section 423 specifies the ID information and the version of each of the sales packages installed on the imaging apparatus 40, and transmits an update request to update the sales package to the package update support section 153 of the component server section 15 ( step S402). In addition, the product ID and version of each sales package are purchased from the installation information management table 427.
[0189] Package update support section 153 determines the sales package (update-target candidate) that can be an update target based on the product ID and the version specified in the update request received and the update table. component management 155. When there is a sales package having the newer version than the version received, which is the sales package registered in component management table 155, the package update support section 153 recognizes the sales package as the target-candidate update-sales package.
[0190] Next, the package update support section 153 causes the dependency relationship determination section 151 to check the sales package dependency relationship of update target candidate (step S404). The reason that the dependency check should be performed after updating although the dependency check has already been performed after installation is that there may be a possibility that the dependency relationship between sales packages is changed due to the update ( update version). In addition, the verification process of verifying the dependency ratio in step 404 is the same as that performed after installation (see figure 33).
[0191] When there is no problem in the dependency relationship, the package update support section 153 generates data from the update list screen to display a screen (update list screen) to select the sales package to be updated among the packages update sales target candidate (step S405). The package update support section 153 then transmits the generated list update screen data to package update section 423 (step S406). On the other hand, when there is a problem in the dependency relationship, confirmation screen data similar to that generated after installation is generated for the sales package of update target candidate, and the generated confirmation screen data is transmitted to the 423 package update.
[0192] Next, package update section 423 enters the received list update screen data for UI control section 426. Based on the screen update data, UI control section 426 controls to display the list update screen on the operation panel 45 (step S407).
[0193] Figure 42 shows an example of displaying the update lists screen. As shown in figure 42, the update list 580 screen includes an update package list 581 display area. In the update package list 581 display area, there is a list of sales packages having the updated versions displayed. In addition, in the list, a check button is provided for each of the sales packages.
[0194] When the check mark button of the sales package to be updated and an update button 582 are pressed by the user (step S408), the package update section 423 specifies the URLs corresponding to the sales packages, and transmits a request for download to download sales packages to download processing section 31 from download server 30 (step S409).
[0195] Namely, the data on the update list screen includes the information item of the respective URLs of the sales packages of update target candidate update. In addition, a download request transmission instruction specifying the marked (selected) sales package URL in the update package list 581 display area is associated with the update button 582.
[0196] The download processing section 31 then acquires a sales package from the sales package management section 32, the sales package being identified by the URL specified in the download request received and transmits the package sales for section update package 423 (step S410). The update package 423 section updates the sales package having an old version for storing the sales package received in a predetermined storage area on the HDD 414. In addition, the update package 423 section updates the package management table 425 (installation information management table 427) based on the product ID information items and the version recorded in the sales package information file stored in the sales package received. Specifically, in the installation information management table 427, a value indicating the version of the product ID is updated.
[0197] The deactivation process is described below. Fig. 43 is a sequence diagram illustrating a procedure for processing the deactivation process.
[0198] In step S501, deactivation section 425 receives an input from a deactivation instruction from a user (step S501). The deactivation instruction is entered through the 560 expansion function management screen (see figure 39). Namely, in the sales package list display area 561 of the expansion function management screen 560, when the sales package to be deactivated is checked and the cancel license button 563 is selected, so that the deactivation section 425 recognize the sales package marked as the deactivation target.
[0199] The deactivation section 425 then specifies the product ID of the selected sales package as the deactivation target and the equipment number of the imaging apparatus 40, and transmits a deactivation request (request for release of license) for deactivation section 116 of activation server section 11 (step S502). Deactivation section 116 changes the registration status related to the specified product ID and equipment number from “in use” to “entry” in the license management table 121. Namely, the information is recorded indicating that the license is not is being used. In addition, deactivation can be performed on the license with the status "in use". Therefore, when the status of the record to be a target is not "in use", the deactivation section 116 determines that the deactivation process has failed.
[0200] Next, the deactivation section 116 transmits a result of the deactivation process (whether the process was successful) to the deactivation section 425 of the imaging apparatus 40 (step S504). When the deactivation process was successful, deactivation section 425 deletes the sales package defined for the deactivation target and the license file 90 corresponding to the sales package from HDD 414 (step S505). In addition, deactivation section 425 deletes the record corresponding to the sales package from the installation information management table 427.
[0201] By doing this, on the image training device 40, the function pack included in the sales pack can no longer be used. On the other hand, once the license of the sales package is released, in the valid period (before the expiration date) of the license, the license can be used in another image training device 40 when necessary. Namely, the deactivation process can be especially effective (useful) when it is desirable that the license of the sales package on a first image training device 40 should be moved to a second image training device (other) 40 of so that the license of the sales package can be used on the second imaging device (other) 40 due, for example, to the validity of the lease period of the first imaging device 40.
[0202] The deactivation process can be automatically performed by the imaging device 40 when an expired license is detected.
[0203] Figure 44 is a flowchart illustrating a procedure for processing an automatic deactivation process on an image-forming device.
[0204] For example, when the imaging device 40 starts or at a predetermined and similar time (YES in step 511), the deactivation section 425 checks the expiration dates (valid periods) of all license folders 90 stored on HDD 414 of the imaging apparatus 40 (step S512). Specifically, deactivation section 425 compares the expiration date and the current date, and determines whether there is an expired license file 90. When determining that there is an expired license file 90 (YES in step S512), the deactivation section 425 performs the deactivation process described with reference to figure 43 in the product ID (sales package) registered in the license file 90 (step S513).
[0205] As described above, according to the first embodiment of the present invention, a user can easily perform the license update process, the sales package update process and the deactivation process based on the screen orientation displayed in the image forming apparatus 40.
[0206] In addition, the sales package entity and the license can be definitively separated (provided separately). Due to this characteristic, it may become possible to flexibly treat, for example, by updating only the license or updating (the version of) only the sales package.
[0207] Next, the edition of the registered group configuration is described. Fig. 45 is a sequence diagram illustrating the processing procedure for a group edit process.
[0208] For example, when an instruction to initiate group change is entered on the sales server 20 by a sales site manager, the product registration section 21 of the sales server 20 transmits an acquisition request to acquire information from group lists for sales server cooperation section 111 of activation server section 11 (step S51). In response to receiving the acquisition request to acquire the group list information, the sales server cooperation section 111 acquires the group list information from the group ID master 120 and the group name master 122 Sales server cooperation section 111 transmits purchased group list information to product registration section 21 (step S52).
[0209] Based on the received group list information, product registration section 21 works to display a group list screen on the sales server display device 20 (step S53). In the group list screen, when any of the groups is selected and the edition is oriented (9th step S54), the product registration section 21 works to display the group 220 edit screen (see figure 16) in which the selected group is defined as an edit target (step S55). Namely, in areas 221 and 222 of the group edit screen 220, the group ID and group name, respectively, of the selected group are displayed.
[0210] Next, in the edit group 220 screen, an edit operation such as additionally adding a sales package to the group, removing a sales package from the group or similar is performed in the group configuration information (step S56) . After the edit operation is complete, and button 228 is clicked (step S57), product registration section 21 transmits a change request to change the group setting for sales server cooperation section 111 (step S58) . The change request to change the group configuration includes parameters such as the group ID and the group name of the group defined as the target to edit, the changed (updated) group configuration information (the product ID of the sales package that belongs to the changed (updated) group), the domain name, sales site ID and password stored on the sales server's storage device 20. In response to the change request to change the group setting, the section Sales Server Cooperation Agreement 111 performs the process of changing the group configuration information (step S59). Specifically, for the group defined as the target to edit, the configuration information registered in the group ID master 120 is updated based on the configuration information included in the change request. After the change process is performed for the group, sales server cooperation section 111 transmits the response indicating whether the change process was successful for product registration section 21 (step S60).
[0211] Below, details of step S59 are described. Figure 46 shows a procedure for processing the group change process. As shown in figure 46, steps S59a and S59b are the same as steps 40a and S40b, respectively, in figure 17.
[0212] Next, the sales server cooperation section 111 determines whether a record is registered in the group ID master 120, the record including the group ID and the sales site ID included in the change request to change the group configuration (step S59c). When determining that the record is registered, the sales server cooperation section 111 determines whether the product key (license) for any of the products related to that group is in use (step S59d). Specifically, the product ID of the sales package belonging to the group is acquired from the group ID master 120 based on the group ID included in the change request to change the group's configuration. Next, for the sales package related to the purchased product ID, it is verified whether the license is in use based on the license management table 121 (see figure 20). In this case, whether the license is in use means (refers to) whether the status is "in use". Upon determining that the license is not in use, the sales server cooperation section 111 performs an update (change) process on the group ID master, the update corresponding to the change request to change the group configuration (step S59e ). Specifically, the sales server cooperation section 111 deletes the existing registered product ID corresponding to the group ID and the sales site ID included in the change request to change the group configuration, and records the product ID included in the change request for group ID and sales site ID.
[0213] Next, the sales server cooperation section 111 transmits the response indicating that the group configuration change was successful for product registration section 21 (step S59f). on the other hand, when determining that there is no required parameter in step S59a, when determining that sales server authentication failed in step S59b, when determining that the group ID and sales site ID are not registered in the ID master group 120 in step S59c, or when determining that the product key corresponding to the group ID has already been used in step S59d, the sales server cooperation section 111 transmits an error response indicating that the group configuration change has failed for product registration section 21 (step S59g).
[0214] In addition, for example, in a case where the sales package license type belonging to the group defined as a change request target is registered as the trial license, even when any of the sales package licenses belongs to the group, editing the group (especially adding the sales package to the group) may be allowed. The trial license is provided for a so-called “trial use”. Therefore, even after the use of any of the sales packages that belong to the group has started, by increasing (adding) the sales package to be used for testing by users, one can expect to promote the sale of the products.
[0215] Next, the deletion of the group is described. In the group list screen shown in step S53 of figure 45, when any of the groups is selected and the deletion is instructed, the product registration section 21 transmits a deletion request 9group) to delete a group including the group ID and the sales site ID corresponding to the group selected for the sales server cooperation section 111 of the license management server 10. In response to the deletion request, the sales server cooperation section 111 performs the process indicated in figure 47.
[0216] Figure 47 illustrates the processing procedure for the group deletion process. In figure 47, steps S61a through S61c correspond to steps S59a through S59c, respectively, in figure 46.
[0217] In step S61d, the sales server cooperation section 111 determines whether the group can be deleted based on a record deletion flag including the group ID and the sales site ID included in the deletion request. group. Specifically, when the value of the deletion flag is “ON”, it is determined that the group can be deleted. On the other hand, when the value of the deletion flag is "OFF", it is determined that the group cannot be deleted.
[0218] When determining that the group can be deleted, the sales server cooperation section 111 performs the update (deletion) on the group ID master 120, the update (deletion) corresponding to the group deletion request (step S61e ). Specifically, the sales server cooperation section 111 deletes a record from the group ID master 120, the record including the group ID and the sales site ID included in the group deletion request. In addition, sales server cooperation section 111 deletes the record corresponding to the group ID from group name master 122. The processes in steps S61f and S61g are obvious from those in steps S59f and S59g in figure 46 therefore, their description is omitted.
[0219] As described above, after group registration, the group configuration can be arbitrarily changed on the sales website. However, when the license for any of the sales packages that belongs to the group is in use, changing the group configuration is limited (prohibited). Therefore, it may become possible to have group management information appropriately compatible with the group's status in the market.
[0220] In the following, a second embodiment of the present invention is described. Fig. 48 shows an exemplary configuration of an equipment management system according to the second embodiment of the present invention. In figure 48, the same symbols (reference numbers) are used for the same elements in figure 1, and their descriptions are properly omitted.
[0221] As shown in figure 48, in user environment E1, an equipment management device 60 is additionally provided. The equipment management apparatus 6 0 is a computer such as a PC (Personal computer) which, for example, collectively purchases and installs the components operating on the imaging apparatus 40 and the licenses (use authorization) of the components. The hardware configuration of the equipment management device 60 can be the same as shown in figure 6. However, the equipment management device 60 includes a display device such as a liquid crystal display and an input device such as a keyboard, a mouse and similar. Equipment management apparatus 60 is connected to each of the imaging apparatus 40 via a network 70 as a LAN (Local Area Network) (wireless or via a wired connection). In addition, user PC 50 can be connected to network 70. In addition, user PC 50 can serve as equipment management device 60 as well.
[0222] Figure 49 shows an exemplary functional configuration of the equipment management apparatus 60 according to the second embodiment of the present invention.
[0223] As shown in figure 49, equipment management apparatus 60 includes a UI control section 611, a package information acquisition section 612, a equipment information acquisition section 613, a receiving section installation target 614, a validity verification section 615, a package acquisition section 616, a license acquisition section 617, an installation control section 618, an uninstall target determination section 619, a section of disable control 620, an uninstall control section 621 and the like. These sections are carried out by a process causing the CPU of the equipment management device 60 to run a relevant program installed on the equipment management device 60.
[0224] The UI 611 control section receives instruction from a user (for example, an instruction to install or uninstall the sales package). The package information acquisition section 612 acquires sales package configuration information having been defined as an installation target or an uninstall target from the license management server 10. The equipment information acquisition section 613 acquires equipment information from the imaging apparatus 40. The equipment information includes the sales package information and the firmware installed on the imaging apparatus 40. Installation target receiving section 614 receives an entry from of a user, the entry specifying the imaging apparatus 40 as the installation destination of the sales package. The validity verification section 615 causes the dependency relationship determination section 151 of the license management server 10 to perform the verification process of verifying the installation validity of the sales package defined as the installation target to be installed. on the imaging apparatus 40 defined as the installation destination.
[0225] The package acquisition section 616 downloads (acquires) the sales package defined as the installation destination from the download server 30. License acquisition section 617 acquires the license file 90 related to the package sales set as the installation target from the license management server 10. Installation control section 618 transmits the sales package and license file 90 to the imaging apparatus 40.
[0226] The uninstallation determination section 619 determines the imaging device 40 on which the sales package defined as an uninstallation target has been installed. The deactivation control section 620 transmits a delete request to delete license file 90 to the imaging apparatus 40 and transmits a license release request to release the license related to license folder 90 to the management server License 10. Uninstall control section 621 broadcasts an uninstall request to uninstall the sales package for the imaging device 40.
[0227] In addition, the functional configurations of the other devices such as the license management server 10, the download server 30, the imaging device 40 and the like can be the same as those in the first embodiment of the present invention.
[0228] Below, a procedure for processing an equipment management system 2 is described. Fig. 50 is a sequence diagram illustrating a procedure for processing the installation and activation of the sales package according to the second embodiment of the present invention. In figure 50, it is assumed that a user of the imaging apparatus 40 has purchased any of the products related to a sales package and has already acquired the product key for the product (purchased). The product purchase method and the product key acquisition method can be the same as the purchase method and the acquisition method in the first embodiment of the present invention. In addition, equipment management apparatus 60 is assumed to be an operating target.
[0229] After receiving a start instruction to begin installing the sales package through an initial screen displayed on the display device, UI 611 control section of equipment management device 60 controls to display the input screen of product key on the display device (step S601). When the product key for the sales package to be installed (hereinafter referred to as a “current sales package”) is entered via the product key entry screen by a user (step S602), the information acquisition section Package ID 612 specifies the incoming product key, and transmits an acquisition request to acquire product key package information to installation support section 152 of license management server 10 (step S603).
[0230] In response to receiving the purchase request to acquire the package information, the installation support section 152 of the license management server 10 causes the product key verification section 113 to verify the effectiveness of the license key. product by executing the processing procedure same as in steps S153 to S155 of figure 22.
[0231] Upon determining that the product key is in effect, installation support section 152 acquires the registered information corresponding to the product key received from component management table 155 (see figure 22), and transmits the information acquired for the 612 package information acquisition section as the package information (step S604). Therefore, the package information includes the product ID associated with at least the product key (that is, the product ID of the current sales package). In addition, when the product key is related to the group license or the volume license, the information related to the various product Ids (multiple records) is included in the package information.
[0232] When the package information is received by the package information acquisition section 612, the UI control section 611 of the equipment management device 60 controls to display a screen (confirmation screen) including the received package information , so that the user can check the contents of the current sales package as well as the contents of the corresponding license (step S605).
[0233] When a continuing instruction to continue the installation operation is entered by the user (for example, when the OK button on the confirmation screen is pressed), the installation destination receiving section 614 works to display a selection screen of equipment including a list of the imaging apparatus 40 on the display device, so that the user can select the imaging apparatus on which the current sales package is to be installed (step S606). In the equipment selection screen, several image formation devices 40 can be selected. In addition, on the equipment selection screen, it is assumed that an imaging device 40 is defined as a display target when information items such as the IP address and host name of the imaging device 40 are stored in the storage device. Otherwise, the equipment information acquisition section 613 can send a broadcast or similar signal to network 70 to dynamically search (detect) the image formation device 40 connected to network 75, so that the name of host or similar of the detected imaging apparatus 40 can be displayed on the equipment selection screen.
[0234] Next, the equipment information acquisition section 613 transmits an acquisition request to acquire equipment information for each image forming device 40 selected on the equipment selection screen (step S607). The installation section 421 of each of the image formation devices 40, having received the acquisition request to acquire the equipment information, acquires the information registered in the installation information management table 427 (see figure 28), and transmits the information including the acquired information and the equipment number of the image forming apparatus 40 for the equipment information acquisition section 613 as the equipment information (step S608).
[0235] Then, in step S609, a looping process is performed for each of the image forming devices 40 that the equipment information of the same is acquired (that is, that is selected in the equipment selection screen). Next, an imaging device 40 on which the looping process is to be performed is called "current equipment".
[0236] In step S609-1, the validity verification section 615 transmits a validity verification request to the license management server 10, the validity verification request including the equipment information of the current equipment and the information of package acquired by the 612 package information acquisition section. Here, "validity" refers to the validity in terms of installing the function package on the current equipment, the function package being included in the current sales package. In response to receiving the validity check request, the dependency relationship determination section 151 of the license management server 10 verifies the dependency relationship of the current sales package by performing a process similar to the process described with reference to figure 33 above. When determining that there is no problem in the dependency relationship, the dependency relationship determination section 151 determines that there is validity. On the other hand, when determining that there is no problem in the dependency relationship, the dependency relationship determination section 151 determines that there is no validity.
[0237] Next, the dependency relationship determination section 151 transmits the validity check result to the validity check section 615 (step S609-2). When determining that there is validity and that a trust package is not installed on the current equipment, the verification result includes the information recorded in component management table 155 for the trust package (hereinafter such a trust package is called “a trust package not introduced ”). This information corresponds to the purchase instruction to purchase the untried trusted package.
[0238] After receiving the verification result indicating that it is valid, the 616 package acquisition section transmits a download request to download the current sales package based on the download path (URL) included in the package information for the current sales package (step S609-3). In response to the download request, the download processing section 31 acquires the sales package from the sales package management section 32, the sales package being identified by the URL specified in the download request, and transmits the package sales (step S-609-4). When there are several current sales packages, the download process (steps S609-3 and S609-4) is repeated several times. In addition, when the verification result including the package information for the untried trust package is received in step S609-2, the download for the untried trust package is also performed. In addition, the case where there are several current packages refers to the case where the product key entered in step S601 is related to the group license, where the various product keys are entered or similar.
[0239] Next, license acquisition section 617 specifies the product key entry in step S601, the product ID of the current sales package, and the equipment number of the current equipment and transmits a license usage request for license management server 10 (step S609-5).
[0240] License issue section 115 of license management server 10 generates license file 90 by performing a process similar to the one in figure 35, and transmits generated license file 90 to license acquisition section 617 ( step S609-6).
[0241] In addition, when the purchase (download) of the sales package by the package acquisition section 616 was successful, the license acquisition section 617 performs the process of step S609-5. Namely, when the sales package was not normally purchased, license purchase section 617 does not acquire license file 90. When the sales package cannot be purchased, the sales package cannot be installed. However, if the license related to the sales package is purchased, use of the license may begin for the sales package that is not actually being used. In such cases the user may have to suffer irrational loss.
[0242] Next, when the untried trust package is purchased in step S609-4, installation control section 618 transmits the untried trust package to the current equipment and transmits a request to install the untried trust package to the current equipment (step S609-7). Installation section 421 of the current equipment installs the untried trust package and records the information (for example, product ID) of the untried trust package in the installation information management table 427.
[0243] Next, the installation control section 618 queries the current equipment about the installation result of the package not introduced (step S609-8). This query (poll) is repeated until the installation is completed on the current equipment, and the installation result is transmitted.
[0244] The reason why the untrusted trusted package is installed first is to avoid the case where the sales package installation failed because the sales package dependent component is not installed (cannot be detected by the sales package).
[0245] Next, installation control section 618 transmits the sales package (current sales package) purchased in step S609-4 and license file 90 acquired in step S 604-6 for the current equipment, and transmits a request for the installation and activation of the sales package for the current equipment (step S609-9). Installation section 421 of the current equipment performs the process on the sales package received and the license file 90, the process being described with reference to figure 22. As a result, the sales package can be used on the current equipment.
[0246] Next, installation control section 618 queries the current equipment on the result of installing the sales package (step S609-10). This query (poll) is repeated until the installation is completed on the current equipment, and the installation result is transmitted.
[0247] Below, the processes for uninstalling and deactivating (license release) the sales package are described.
[0248] Figure 51 is a sequence diagram illustrating a procedure for processing the uninstallation and deactivation processes according to the second embodiment of the present invention.
[0249] In step S701, UI control section 611 of equipment management device 60 receives the entry of the product key to be uninstalled through the uninstallation screen displayed on the display device by a user. The package information acquisition section 612 then specifies the entered product key, and transmits an acquisition request to acquire the package information related to the product key to the license management server 10 (step S702).
[0250] Next, component management section 154 of license management server 10 performs the process similar to that performed in response to step S603 in figure 50, and transmits package information from the sales package related to the product key received for the package information acquisition section 612 (step S703). When the product key is related to the group license, the package information for the various sales packages is transmitted.
[0251] When the product key is related to the group license, namely, when the package information related to the various sales packages is received, the UI 611 control section controls to display a sales package selection screen including a list of sales packages on the display device, so that the user can select the sales package to be uninstalled (step S704). In the following, the selected sales package refers to a “current sales package”.
[0252] Next, the equipment information acquisition section 612 transmits an acquisition request to acquire the equipment information for each of the imaging apparatus 40 (step S705). In response to the acquisition request to acquire the equipment information, the deactivation section 425 of each of the imaging apparatus 40 acquires the information recorded in the installation information management table 427, and transmits the acquired information and the information including the equipment number of the image forming apparatus 40 itself for the equipment information acquisition section 613 as the equipment information (step S706).
[0253] Next, the uninstall destination determination section 619 compares (verifies) the package information acquired in step S7093 with the equipment information of the imaging apparatus 40 acquired in step S706, and determines the training apparatus image 40 in which sales package related to package information is installed (step S707). Specifically, the imaging apparatus 40 related to equipment information including the product ID included in the packaging information (sales package product ID) is determined to be the imaging apparatus 40 on which the sales package is. installed (that is, the imaging device 40 from which the sales package is to be uninstalled).
[0254] Then, in step S708, a looping process is performed for each of the imaging devices 40 from which the sales package must be uninstalled. Next, the image forming apparatus 40 to be processed in the loop process is called "current equipment".
[0255] In step S708-1, the deactivation control section 620 specifies the product ID of the current sales package, and transmits a deactivation request (a deletion request to delete license file 90) for the current equipment . In response to the request, deactivation section 425 of the current equipment deletes license file 90 related to the specified product ID.
[0256] Next, the deactivation control section 620 queries the current equipment about the process of deleting the license file 90 (step S708-2). This query (poll) is repeated until the process of deleting the license file 90 is completed on the current equipment, and the result of the deletion process is transmitted.
[0257] Next, uninstall control section 621 specifies the product ID of the current sales package, and transmits an uninstall request (a delete request to delete the sales package) for the current equipment (step S708- 3). In response to the request, the deactivation section 425 uninstalls (deletes) the sales package related to the specified product ID.
[0258] Next, the deactivation control section 620 queries the current equipment about the result of uninstalling the current sales package. This query (poll) is repeated until the process of uninstalling license file 90 is completed on the current equipment and the uninstallation result is transmitted.
[0259] After step S708 is performed for all imaging devices 40 from which the sales package is to be uninstalled, the deactivation control section 620 specifies the product ID of the current sales package and the numbers of equipment from all imaging devices 40 and transmits a deactivation request (license release request) to deactivation section 116 of license management server 10 (step S709). Deactivation section 116 performs the same process as that of step S503 described with reference to figure 43. As a result, the status of the licenses related to the specified product ID and the equipment number is changed to “inbound”. The deactivation section 116 then passes the result of the deactivation process (if successful) to the deactivation control section 620 of the equipment management apparatus 60 (step S710).
[0260] As described above, in the equipment management apparatus 60 according to the second embodiment of the present invention, for example, the installation process and the activation process (start using license) can be collectively performed on various training devices image 40. Therefore, especially in the E1 user environment where there are many 40 imaging devices, it may become possible to significantly reduce the user's operating load.
[0261] Furthermore, in that embodiment of the present invention, the imaging apparatus 40 is described as an example of equipment. However, the scope of the present invention is not limited to the imaging apparatus 40. For example, the present invention can be additionally effectively applied to any apparatus (equipment) where a program can be added (installed).
[0262] In the following, a third embodiment of the present invention is described. Fig. 52 shows an exemplary configuration of an equipment management system according to the third embodiment of the present invention. In figure 52, the same symbols (reference numbers) are used for the same elements in figure 1, and their descriptions are properly omitted.
[0263] As shown in figure 52, in the E1 user environment, a Network 65 client terminal is additionally provided (added). The Network 65 client terminal can be a computer or an electronic device such as a PC (Personal computer) having a network browser. For example, a hardware configuration of the network client terminal 65 may be similar to that in figure 6. However, the network client terminal 65 includes a display device such as a liquid crystal display and an input device such as a keyboard. , a mouse and the like. The network client terminal 65 is connected to each of the imaging apparatus 40 via a network 75 as a LAN (Local Area Network) (wireless or via a wired connection). In addition, user PC 50 can be connected to network 75. In addition, user PC 50 can serve as network client terminal 65.
[0264] Figure 453 shows an exemplary functional configuration of an equipment management apparatus according to the third embodiment of the present invention. In figure 53, the same symbols (reference numbers) are used for the same elements in figure 5, and their descriptions are properly omitted.
[0265] As shown in figure 53, the imaging apparatus 40 further includes a network server section 428. The network server section 428 performs a process of displaying the screens on the network client terminal 65, the screens being displayed on the operation panel 45 by the UI control section 426. Specifically, the network server section 428 transmits each HTML data from the screens to the network client terminal 65.
[0266] On the other hand, the network client terminal 65 includes a network browser 651. The network browser 651 receives the HTML data transmitted from the network server section 428, and displays multiple screens based on the HTML data on the display device of the network client terminal 651.
[0267] Namely, in the equipment management system 3 according to the third embodiment of the present invention, a user can remotely perform operations through the network client terminal 65, the operations being the same as those performed using the operation panel 45 as described in the first embodiment of the present invention. Specifically, the user can execute the instruction inputs in steps S151, S159 and S165 of the sequence diagram of figure 22 through the screen displayed by the network browser 651. Therefore, in this third embodiment, the network server section 428 corresponds to a example of an input medium that receives the license key input.
[0268] Furthermore, in each of the above embodiments, the license management server 10, the sales server 20, and the download server 30 are described as separate devices. However, for example, license server 10 can include at least anyone between sales server 20 and download server 30.
[0269] According to a fourth embodiment of the present invention, a license management method is performed by a sales management appliance and a license management appliance that manages a license for a program sold by the sales management appliance, the method including:
[0270] A group registration request step where the sales management device displays a list of information from one or more programs, and transmits a registration request to the license management device, the registration request including information of setting up a group including a combination of several of the programs selected from the programs in the information list;
[0271] A product registration step where the sales management device receives a license information entry corresponding to the group, associates the license information with the group, and stores the associated license information together with the group in a unit. storage of product information as product information;
[0272] A sales management step where the sales management device transmits a list of product information in response to a receipt of a purchase request to purchase the program, the product information being stored in the information storage unit of product; and
[0273] A step of storing group information where the license management device stores the configuration information included in the registration request.
[0274] According to a fifth embodiment of the present invention, a program is provided encoded and stored in a computer-readable format to make a sales management device and a license management device manage a license for a sold program by the sales management device perform a method including:
[0275] A group registration request step where the sales management device displays a list of information from one or more programs, and transmits a registration request to the license management device, the registration request including information of confirmation of a group including a combination of several of the programs selected from the programs in the information list;
[0276] A product registration step where the sales management device receives an entry of license information corresponding to the group, associates the license information with the group, and stores the associated license information together with the group in a unit of storage of product information as product information;
[0277] A sales management step where the sales management device transmits a list of product information in response to a receipt of a purchase request to purchase the program, the product information being stored in the information storage unit of product; and
[0278] A step of storing group information that the license management device stores the configuration information included in the registration request.
[0279] The present invention is described above as it relates to specific embodiments. However, the present invention is not limited to the embodiments described above, and various modifications, transformations, alterations, exchanges and the like can be made without departing from the scope and spirit of the present invention.
[0280] This application is based on and claims the priority benefit of Japanese patent application no. 2009-253499, filed on November 4, 2009, the entire content of which is hereby incorporated by reference.

权利要求:
Claims (7)
[0001]
1. Sales management appliance comprising: a license management appliance that manages a license for a program sold by the sales management appliance, the license management appliance, including a group information storage unit for storing customer information. configuration included in a registration request sent from the sales management device, characterized by the fact that the sales management device comprises: a transmission unit that is configured to display a list of information from one or more of the programs and transmit the registration request for the license management device, the configuration information in the registration request including information for a group that includes a combination of several of the programs selected from the programs in the information list; a product information storage unit; a product registration unit that is configured to receive an entry of license information corresponding to the group, associate the license information with the group and store the associated license information together with the group for the information product storage unit as the product information; and a sales management unit, which transmits a list of product information, in response to a receipt of a purchase request to purchase the program, the product information to be stored in the information product storage unit; wherein in response to an instruction to change a group configuration, the transmission unit is configured to transmit a group change request to the license management appliance, the change request including configuration information according to the instruction changes and the license management appliance is configured to update the configuration information stored on the information storage group unit based on the configuration information included in the change request as long as a program license included in the group related to the change request. change is not in use.
[0002]
2. Sales management apparatus, according to claim 1, characterized by the fact that the product registration unit is configured to receive an entry of different license information corresponding to the same group and store the product information corresponding to the group in the product information storage unit.
[0003]
3. Sales management device, according to claim 1 or 2, characterized by the fact that the sales management unit is configured to report the group's sales to the license management device, the group corresponding to the information of the group. selected from the product information list, in response to an entry in a group deletion statement, the transmitting unit is configured to transmit a group deletion request to the license management device, and when the related group the deletion request does not match the group related to the group sales reported from the sales management unit, the license management appliance is configured to delete group configuration information related to the deletion request from the storage unit group information.
[0004]
4. License management device configured for use in a license management system comprising a sales management device, the sales management device, managing a license for a program sold by the sales management device, characterized by the fact that that the sales management appliance comprises: a transmission unit that is configured to display a list of information from one or plural of the programs and transmit a registration request to the license management appliance, the registration request including configuration information for a group including a combination of the plural of programs selected from the programs in the information list; a product information storage unit; a product registration unit that is configured to receive a license information entry corresponding to the group, associate the license information with the group, and store the associated license information together with the group in the product information storage unit as product information. product; and a sales management unit that is configured to transmit a list of product information in response to a receipt of a purchase request for the purchase of the program, the product information being stored in the product information storage unit; the license management appliance including: a group information storage unit configured to store the configuration information included in the registration request where in response to an instruction to change a group configuration, the transmission unit is configured to transmit a group change request to the license management device, the change request including configuration information according to the change instruction, and the license management device is configured to update the configuration information stored on the unit storage of group information based on the configuration information included in the change request, provided that a program license included in the group related to the change request is not in use.
[0005]
5. License management device, according to claim 4, characterized by the fact that the product registration unit receives an entry of different license information corresponding to the same group and stores the product information corresponding to the same group in product information storage unit.
[0006]
6. License management device according to claim 4 or 5, characterized by the fact that the sales management unit is configured to report the group's sales to the license management device, the group corresponding to the product information selected in the product information list, in response to an entry in a group deletion statement, the transmitting unit is configured to transmit a group deletion request to the license management device, and when the group relates to the deletion request. deletion does not match the group related to the group's sales reported by the sales management unit, the license management appliance is configured to delete group configuration information related to the request for deletion of the group's information storage unit.
[0007]
7. License management system characterized by the fact that it comprises: a sales management device, as defined in any one of claims 1 to 3; and a license management appliance, as defined in any of claims 4 to 6, configured to manage a license for a program sold by the sales management appliance.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112012010660B1|2020-12-15|LICENSE MANAGEMENT SYSTEM, SALES MANAGEMENT APPARATUS AND LICENSE MANAGEMENT APPARATUS

---

BR112012010663B1|2021-01-05|license management device, method and system

---

EP2396743B1|2017-12-20|License management apparatus, device, and license management method

---

AU2011259889B2|2014-02-13|Information processing device, program installation support method, and computer-readable recording medium

---

JP5428685B2|2014-02-26|License introduction support device, license introduction support method, and license introduction support program

---

JP2012008927A|2012-01-12|Management device, license management server, electronic apparatus, electronic apparatus management system, management method, program, and storage medium

---

EP2284753B1|2018-01-24|Program introduction supporting server, program introduction supporting system, program introduction supporting method, and program introduction supporting computer program

---

US8387156B2|2013-02-26|Equipment managing system, equipment managing method, and computer-readable storage medium

---

JP5708856B2|2015-04-30|License management system, sales management device, license management device, license management method, and program

---

JP5776829B2|2015-09-09|Information processing system, information processing method, information processing apparatus, and program

---

JP2015228230A|2015-12-17|Information processing system, information processing apparatus, program, and information processing method

---

JP2014013619A|2014-01-23|System

---

JP5704219B2|2015-04-22|Device management system and device management method

---

JP2014081946A|2014-05-08|License introduction support system, license introduction support method, and license introduction support program

同族专利:

---

公开号 | 公开日

---

CN102598018B|2015-08-05|

---

AU2010316203A1|2012-05-17|

---

RU2504007C1|2014-01-10|

---

BR112012010660A2|2017-12-05|

---

US20120215662A1|2012-08-23|

---

EP2497061A4|2014-05-14|

---

CN102598018A|2012-07-18|

---

EP2497061A1|2012-09-12|

---

JP2011100226A|2011-05-19|

---

RU2012122760A|2013-12-10|

---

WO2011055836A1|2011-05-12|

---

EP2497061B1|2019-02-27|

---

JP5499642B2|2014-05-21|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

CN100435164C|2001-05-29|2008-11-19|松下电器产业株式会社|Rights management unit|

---

CA2485053A1|2002-05-10|2003-11-20|Protexis Inc.|System and method for multi-tiered license management and distribution using networked clearinghouses|

---

US7356709B2|2003-01-31|2008-04-08|Microsoft Corporation|Systems and methods for deterring software piracy in a volume license environment|

---

US7231370B1|2004-10-27|2007-06-12|Lsi Corporation|Method and apparatus for organizational software license sharing|

---

US20060170759A1|2005-02-03|2006-08-03|Navio Systems Inc.|Methods and apparatus for optimizing digital asset distribution|

---

US7890428B2|2005-02-04|2011-02-15|Microsoft Corporation|Flexible licensing architecture for licensing digital application|

---

US8091142B2|2005-04-26|2012-01-03|Microsoft Corporation|Supplementary trust model for software licensing/commercial digital distribution policy|

---

WO2007031985A2|2005-09-15|2007-03-22|Digital Layers Inc.|A method, a system and an apparatus for delivering media layers|

---

US20090276334A1|2006-04-18|2009-11-05|Kotaro Hosoda|Content purchasing/viewing system, content reproducing device, and content reproduction authentication server|

---

US20140304129A1|2006-10-23|2014-10-09|Juan-Carlos Colosso|Surrender and management of software licenses|

---

US20090037287A1|2007-07-31|2009-02-05|Ahmad Baitalmal|Software Marketplace and Distribution System|

---

US8103559B2|2008-02-15|2012-01-24|International Business Machines Corporation|Maintenance of group shared inventories in a virtual universe|

---

JP2009251977A|2008-04-08|2009-10-29|Nec Corp|Software installation system|

---

RU81824U1|2008-10-23|2009-03-27|Александр Алексеевич Бойко|ELECTRONIC BANK WARRANTY SYSTEM|JP5335852B2|2011-04-27|2013-11-06|周 市原|Extracted slice auxiliary tool and auxiliary device|

---

JP5847552B2|2011-11-17|2016-01-27|キヤノン株式会社|Management apparatus, information processing system, and management method|

---

JP5320615B1|2012-04-28|2013-10-23|桂子 竹田|Content quality arrangement device and program thereof|

---

JP6007075B2|2012-11-16|2016-10-12|任天堂株式会社|Service providing system, service providing method, server system, and service providing program|

---

US8763159B1|2012-12-05|2014-06-24|Parallels IP Holdings GmbH|System and method for application license management in virtual environments|

---

CN104142928A|2013-05-07|2014-11-12|中国科学院寒区旱区环境与工程研究所|Data offline method and data offline device for scientific data sharing platform|

---

JP6387699B2|2014-06-17|2018-09-12|富士通株式会社|License management auxiliary program, method and apparatus|

---

JP6068421B2|2014-11-21|2017-01-25|京セラドキュメントソリューションズ株式会社|Maintenance server, maintenance method and license / maintenance management server|

---

CN104915766A|2015-05-31|2015-09-16|镇江东软信息技术有限公司|Vehicle sales system sales management module|

---

JP2017204242A|2016-05-13|2017-11-16|キヤノン株式会社|Information processing apparatus, programmable device, license management system, license management method, and program|

---

US10638012B2|2016-07-14|2020-04-28|Ricoh Company, Ltd.|Information processing system, information processing apparatus, and information processing method|

---

JP6499730B2|2017-07-19|2019-04-10|ファナック株式会社|Application sales management server system and edge server|

---

JP6499729B2|2017-07-19|2019-04-10|ファナック株式会社|Application sales management server system|

---

JP6608878B2|2017-07-19|2019-11-20|ファナック株式会社|Application sales management server system|

---

JP6640798B2|2017-07-31|2020-02-05|グリー株式会社|Application usage management program, application usage management method, server, management program, and management user terminal|

---

JP6978487B2|2017-07-31|2021-12-08|グリー株式会社|Application usage management system, application management program, application management method, control program, control method, and server|

---

JP2019045903A|2017-08-29|2019-03-22|キヤノン株式会社|Management apparatus, control method, and program|

---

DE102020201526A1|2019-03-05|2020-09-10|Fanuc Corporation|OVERSEAS COMPATIBLE APPLICATION DISTRIBUTION MANAGEMENT SYSTEM|

法律状态:
2018-03-27| B15K| Others concerning applications: alteration of classification|Ipc: G06Q 50/00 (2012.01), G06F 21/00 (2013.01), G06Q 3 |

---

2019-01-08| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|

---

2019-07-30| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

---

2020-05-26| B06A| Notification to applicant to reply to the report for non-patentability or inadequacy of the application [chapter 6.1 patent gazette]|

---

2020-09-01| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|

---

2020-12-15| B16A| Patent or certificate of addition of invention granted|Free format text: PRAZO DE VALIDADE: 10 (DEZ) ANOS CONTADOS A PARTIR DE 15/12/2020, OBSERVADAS AS CONDICOES LEGAIS. |

优先权:

---

申请号 | 申请日 | 专利标题

---

JP2009-253499|2009-11-04|

---

JP2009253499A|JP5499642B2|2009-11-04|2009-11-04|License management system, sales management device, license management device, license management method, and program|

---

PCT/JP2010/069877|WO2011055836A1|2009-11-04|2010-11-02|License management system, sales management apparatus, and license management apparatus|

---